﻿<?xml version="1.0" encoding="utf-8"?>
<cmdlets>
  <cmd>
    <name> Add-SPClaimTypeMapping </name>
    <synopsis><![CDATA[ Adds a claim mapping to a trusted security token service (STS) identity provider. ]]></synopsis>
    <description>
      <![CDATA[ The Add-SPClaimTypeMapping cmdlet adds a claim type mapping rule to a security token service (STS) identity provider from a farm 
trust STS authentication provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[

Add-SPClaimTypeMapping [-Identity] <SPClaimMappingPipeBind> [-TrustedIdentityTokenIssuer] <SPTrustedIdentityTokenIssuerPipeBind> [-Assig
nmentCollection <SPAssignmentCollection>] [-Force <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTrustedIdentityProvider -Name "LiveIDSTS" | Add-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05
/identity/claims/nameidentifier" -IncomingClaimTypeDisplayName "PUID" -LocalClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/cl
aims/thumbprint"
]]>
        </Code>
        <Remarks> This example adds a claim mapping to a trusted identity token issuer </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPDiagnosticsPerformanceCounter </name>
    <synopsis><![CDATA[ Adds a new instance of a performance counter to a Web front end computer or a database server. ]]></synopsis>
    <description>
      <![CDATA[ The Add-SPDiagnosticsPerformanceCounter cmdlet adds a performance counter to a Web front end computer on a database server. A per
formance counter is read and recorded in the Usage Database. By default, the new performance counter is added to the database servers in 
the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Add-SPDiagnosticsPerformanceCounter [-Category] <String> -Counter <String> [-AllInstances <SwitchParameter>] [-AssignmentCollection <SPA
ssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseServer <SwitchParameter>] [-WebFrontEnd <SwitchParameter>] [-WhatIf [<Swi
tchParameter>]] [<CommonParameters>]
Add-SPDiagnosticsPerformanceCounter [-Category] <String> -Instance <String> [-AllInstances <SwitchParameter>] [-AssignmentCollection <SP
AssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Counter <String>] [-DatabaseServer <SwitchParameter>] [-WebFrontEnd <SwitchParam
eter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPDiagnosticsPerformanceCounter -category ASP.NET -Counter "Requests Queued"
]]>
        </Code>
        <Remarks> This example adds the counter with the name ASP.NET\Requests Queued on Web front end computers </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPDiagnosticsPerformanceCounter -category PhysicalDisk -counter "Avg. Disk Queue Length" -allinstances
]]>
        </Code>
        <Remarks> This example adds all instances of the counter PhysicalDisk in the category Avg. Disk Queue Length on Web front ends computers </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPDiagnosticsPerformanceCounter -category Processor -counter "% Processor Time" -instance "_Total" -databaseserver
]]>
        </Code>
        <Remarks> This example adds the _Total instance of the counter % Processor Time in the category Processor on database servers </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPInfoPathUserAgent </name>
    <synopsis><![CDATA[ Adds a user agent to a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Add-SPInfoPathUserAgent cmdlet creates a user agent to receive the .xml file that contains the data of the form for indexing.
 The user agent receives the InfoPath 2010 files from InfoPath Forms Services in Microsoft SharePoint Server 2010 instead of Web pages in
 response to an HTTP request For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Add-SPInfoPathUserAgent -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<Switch
Parameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPInfoPathUserAgent -Name "NewAgent"
]]>
        </Code>
        <Remarks> This example creates a new agent named NewAgent </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPPluggableSecurityTrimmer </name>
	  <synopsis></synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Add-SPPluggableSecurityTrimmer [-UserProfileApplicationProxyId] <Guid> -PlugInId <Int32> [-QualifiedTypeName <String>] [-CustomPropertie
s <NameValueCollection>] [-AssignmentCollection <SPAssignmentCollection>] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-Warnin
gAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>] [-WhatIf]
 [-Confirm]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPServiceApplicationProxyGroupMember </name>
    <synopsis><![CDATA[ Adds a member to the service application proxy group. ]]></synopsis>
    <description>
      <![CDATA[ The Add-SPServiceApplicationProxyGroupMember cmdlet adds a member to the service application proxy group For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Add-SPServiceApplicationProxyGroupMember [-Identity] <SPServiceApplicationProxyGroupPipeBind> [-Member] <SPServiceApplicationProxyPipeBi
nd[]> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPServiceApplicationProxyGroupMember RemoteProxyGroup -Member babab30e-8e3a-428b-8ff4-4d5c8f455e6d
]]>
        </Code>
        <Remarks>
          This example adds a select service application proxy to the service application proxy group named RemoteProxyGroup The service application proxy group GUID is unique to every farm. You can run Get-SPServiceApplicationProxyGroup | Select Name,Id
          to see the GUID of the serviceapplication proxy groups. Use this result for any other SPServiceApplicationProxyGroup cmdlets
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPShellAdmin </name>
    <synopsis><![CDATA[ Adds a user to the SharePoint_Shell_Access role for the specified database. ]]></synopsis>
    <description>
      <![CDATA[ Use the Add-SPShellAdmin cmdlet to add a user to the SharePoint_Shell_Access role for a specified database. You must run the Add-
SPShellAdmin cmdlet for all databases that you want to grant access to. If no database is specified, the farm configuration database is u
sed. If you do specify a database, the farm content database will be included in addition to the farm configuration database you specify.
} } A user cannot run Windows PowerShell cmdlets in a farm unless you have used this cmdlet to add the user to the SharePoint_Shell_A
ccess role. When a user has been added to the SharePoint_Shell_Access role and is a member of the WSS_Admin_WPG group, then the user can 
run Windows PowerShell in a multiple-server farm environment When you run this cmdlet to add a user to the SharePoint_Shell_Access role, the user must have the following security permissions
:} } - Security_Admin role access on the SQL instance and the db_owner role in a database - Administrative permission to the local computer The user is added to the WSS_Admin_WPG group in all front-end Web servers when the user is added to the SharePoint_Shell_Access r
ole. If the target database does not have a SharePoint_Shell_Access role, the role is automatically created For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Add-SPShellAdmin [-UserName] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-database <SPData
basePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE 1------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPShellAdmin -UserName CONTOSO\User1
]]>
        </Code>
        <Remarks>
          This example adds a new user named User1 to the SharePoint_Shell_Access role in the farm configuration database only, and also en
          sures the user is added to the WSS_Admin_WPG local group on each server in the farm
        </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 2------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPShellAdmin -UserName CONTOSO\User1 -database WSS_Content
]]>
        </Code>
        <Remarks>
          This example adds a new user named User1 to the SharePoint_Shell_Access role in both the specified content database and the confi
          guration database, and also ensures the user is added to the WSS_Admin_WPG local group on each farm server
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPSiteSubscriptionFeaturePackMember </name>
    <synopsis><![CDATA[ Adds a feature to a SharePoint Feature set. ]]></synopsis>
    <description>
      <![CDATA[ The Add- SPSiteSubscriptionFeaturePackMember cmdlet adds features to the provided SharePoint Feature set. Feature sets are an All
ow List of  SharePoint Features that can be associated with any site subscription. If a Feature set is assigned to a site subscription, o
nly the SPFeatures object in that Feature set are available for use on the site collections and Web sites that are members of the site su
bscription. Feature sets contain a list of the GUIDs of each Feature that are on the Allow List for associated site subscriptions For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Add-SPSiteSubscriptionFeaturePackMember [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> -FeatureDefinition <SPFeatureDefinitionPipeB
ind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>$fs = New-SPFeatureSet

C:\PS>Get-SPFeature -limit all | Where{ $_.Scope -eq "WEB" } | Add-SPFeatureSetMember -id $fs

C:\PS>$fs = Get-SPFeatureSet $fs
]]>
        </Code>
        <Remarks> This example creates a Feature set and adds all Web site scoped Features to the set The Feature set is refreshed in the last line so that the local object has the correct values </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPSiteSubscriptionProfileConfig </name>
    <synopsis><![CDATA[ Adds a new site subscription to a User Profile Service application. ]]></synopsis>
    <description><![CDATA[ The Add-SPSiteSubscriptionProfileConfig cmdlet adds a new site subscription to a User Profile Service application ]]></description>
    <syntax>
      <![CDATA[
Add-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> -ProfileServiceApplicationProxy <SPServiceApplicationProxyP
ipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MySiteHostLocation <SPSitePipeBind>] [-Synchr
onizationOU <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Add-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> -MySiteHostLocation <SPSitePipeBind> -ProfileServiceApplica
tionProxy <SPServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MySiteHo
stLocation <SPSitePipeBind>] [-MySiteManagedPath <SPPrefixPipeBind>] [-SiteNamingConflictResolution <String>] [-SynchronizationOU <Strin
g>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>#Get UPA Proxy
$pr = Get-SPServiceApplicationProxy | ? {$_.DisplayName.Contains(PartitionedUserProfileApplication_Proxy)}

C:\PS>#Add tenant to UPA 
Add-SPSiteSubscriptionProfileConfig -Identity $sub -ProfileServiceApplicationProxy $pr -MySiteHostLocation http://contoso/my

C:\PS>#Create new site subscription
$sub = New-SPSiteSubscription
]]>
        </Code>
        <Remarks> This example creates a new User Profile Service application tenant </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPSolution </name>
    <synopsis><![CDATA[ Uploads a SharePoint solution package to the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Add-SPSolution cmdlet adds a SharePoint solution package to the farm. This cmdlet does not deploy the uploaded SharePoint sol
ution. Use the Install-SPSolution cmdlet to deploy the SharePoint solution in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Add-SPSolution [-LiteralPath] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Language <UInt3
2>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPSolution -LiteralPath c:\contoso_solution.wsp
]]>
        </Code>
        <Remarks> This example adds the SharePoint solution in the file contoso_solution.wsp to the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Add-SPUserSolution </name>
    <synopsis><![CDATA[ Uploads a new sandboxed solution to the solution gallery. ]]></synopsis>
    <description>
      <![CDATA[ The Add-SPUserSolution cmdlet uploads a new sandboxed solution package to the solution gallery. This cmdlet does not activate the
 uploaded sandboxed solution; to activate the solution in the site collection, use the Install-SPUserSolution cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Add-SPUserSolution [-LiteralPath] <String> -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPar
ameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Add-SPUserSolution -LiteralPath c:\contoso_solution.wsp -Site http://sitename
]]>
        </Code>
        <Remarks> This example adds the sandboxed solution c:\contoso_solution.wsp to the site http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Backup-SPConfigurationDatabase </name>
    <synopsis><![CDATA[ Performs a farm-level configuration-only backup. ]]></synopsis>
    <description>
      <![CDATA[ The Backup-SPConfigurationDatabase cmdlet performs a configuration-only backup of the current farm or a configuration-only backup
 of a separate configuration database which is not attached to the current farm. If you wish to perform a configuration-only backup of th
e current farm, there is no need to specify the DatabaseServer and DatabaseName parameters. However, using the Backup-SPFarm cmdlet with 
the ConfigurationOnly parameter is recommended for such a scenario An example of a configuration backup is an administrator creates a farm configuration template which then can be applied to other
 SharePoint farms by performing a restore using the Restore-SPFarm cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Backup-SPConfigurationDatabase -Directory <String> [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseCredentials <PSCredential>
] [-DatabaseName <String>] [-DatabaseServer <String>] [-Item <String>] [<CommonParameters>]
Backup-SPConfigurationDatabase -ShowTree <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseCredentials <PSCre
dential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-Item <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE 1-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Backup-SPConfigurationDatabase -DatabaseName SharePoint_Config -DatabaseServer SqlServer1 -Directory \\server\share\Backup -ShowTr
ee
]]>
        </Code>
        <Remarks> This example displays components that are available for inclusion in a configuration-only backup </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 2-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Backup-SPConfigurationDatabase -DatabaseName SharePoint_Config -DatabaseServer SqlServer1 -Directory \\server\share\Backup -Verbos
e
]]>
        </Code>
        <Remarks> This example performs a configuration-only backup with verbose output </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Backup-SPFarm </name>
    <synopsis><![CDATA[ Creates a backup of an individual database, Web application, or the entire farm. ]]></synopsis>
    <description>
      <![CDATA[ The Backup-SPFarm cmdlet creates a backup for the entire farm or individual components within the farm. It can also be used to ba
ck up just the configuration settings of a farm to be used as a farm template for other SharePoint farms.If you want to back up a single 
site collection, use the Backup-SPSite cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Backup-SPFarm -BackupMethod <String> -Directory <String> [-AssignmentCollection <SPAssignmentCollection>] [-BackupThreads <Int32>] [-Con
figurationOnly <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-Item <String>] [-Percentage <Int32>] [-Wha
tIf [<SwitchParameter>]] [<CommonParameters>]
Backup-SPFarm -ShowTree <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-ConfigurationOnly <SwitchParameter>] [-Conf
irm [<SwitchParameter>]] [-Item <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE 1--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Backup-SPFarm -Directory \\file_server\share\Backup -BackupMethod full -ConfigurationOnly
]]>
        </Code>
        <Remarks> This example backs up the configuration settings of the farm to the \\file_server\share\Backup directory </Remarks>
      </example>
      <example>
        <title> --------------------EXAMPLE 2--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Backup-SPFarm -ShowTree -Item "Microsoft SharePoint Foundation Web Application" -Verbose
]]>
        </Code>
        <Remarks>
          This example shows which components of the farm would be backed up under the "Microsoft SharePoint Foundation Web Application" no
          de, but do not actually back them up
        </Remarks>
      </example>
      <example>
        <title> --------------------EXAMPLE 3--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Backup-SPFarm -Directory C:\Backup -BackupMethod full -BackupThreads 10 -Force
]]>
        </Code>
        <Remarks>
          This example performs a backup of a farm using 10 threads and forces the backup to be saved to the C:\Backup directory even thoug
          h SharePoint estimates that it does not have sufficient space available
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Backup-SPSite </name>
    <synopsis><![CDATA[ Performs a backup of a site collection. ]]></synopsis>
    <description>
      <![CDATA[ The Backup-SPSite cmdlet performs a backup of the site collection when the Identity parameter is used By default, the site collection will be set to read-only for the duration of the backup to reduce the potential for user activity
 during the backup operation to corrupt the backup. If you have SQL Server Enterprise Edition, we recommend that UseSqlSnapshot parameter
 be used because this ensures a valid backup while it allows users to continue reading and writing to the site collection during the back
up For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Backup-SPSite [-Identity] <SPSitePipeBind> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]
] [-Force <SwitchParameter>] [-NoSiteLock <SwitchParameter>] [-UseSqlSnapshot <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonP
arameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE 1-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Backup-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak
]]>
        </Code>
        <Remarks> This example backs up a site collection at http://server_name/sites/site_name to the C:\Backup\site_name.bak file </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 2-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteAdministration http://server_name/sites/site_name | Backup-SPSite -Path C:\Backup\site_name.bak
]]>
        </Code>
        <Remarks>
          This example backs up a site collection at http://server_name/sites/site_name to the C:\Backup\site_name.bak file. Same result as
          Example 1, but a different way of performing the operation
        </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 3-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Backup-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak -UseSqlSnapshot
]]>
        </Code>
        <Remarks> This example backs up a site collection using database snapshots to ensure backup integrity </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Clear-SPLogLevel </name>
    <synopsis><![CDATA[ Resets the Windows trace logging and event logging levels to their default values. ]]></synopsis>
    <description>
      <![CDATA[ The Clear-SPLogLevel cmdlet resets the Windows event logging and trace logging levels for the specified categories to the default
 values. If the Identity parameter is not provided, all categories are affected For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Clear-SPLogLevel [-AssignmentCollection <SPAssignmentCollection>] [-Identity <String[]>] [-InputObject <PSObject>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Clear-SPLogLevel -Identity Cat1
]]>
        </Code>
        <Remarks> This example resets the log levels for a single category </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>"Cat1", "Cat2", "Cat3" | Clear-SPLogLevel
]]>
        </Code>
        <Remarks> This example resets the log levels for multiple categories </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogLevel | Clear-SPLogLevel
]]>
        </Code>
        <Remarks> This example resets the log levels for all categories </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Clear-SPMetadataWebServicePartitionData </name>
    <synopsis><![CDATA[ Removes all data for a site subscription on a metadata Web service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Clear-SPMetadataWebServicePartitionData cmdlet to clear all data for a site subscription on a metadata Web service applic
ation For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Clear-SPMetadataWebServicePartitionData -Identity <SPSiteSubscriptionPipeBind> -ServiceProxy <SPMetadataServiceProxyCmdletPipeBind> [-As
signmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Clear-SPMetadataWebServicePartitionData -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2"
]]>
        </Code>
        <Remarks> This example removes data for a site subscription on a Metadata Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Clear-SPPerformancePointServiceApplicationTrustedLocation </name>
    <synopsis><![CDATA[ Clears all the trusted locations for a PerformancePoint Service application identity. ]]></synopsis>
    <description>
      <![CDATA[ The Clear-SPPerformancePointServiceApplicationTrustedLocation cmdlet removes all the trusted locations for a PerformancePoint Ser
vice application. Use the TrustedLocationType parameter to remove only the trusted locations for a trusted location type For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Clear-SPPerformancePointServiceApplicationTrustedLocation -ServiceApplication <SPPerformancePointMonitoringServiceApplicationPipeBind> [
-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-TrustedLocationType <DataSource | Content>] [-WhatIf [<
SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Clear-SPPerformancePointServiceApplicationTrustedLocation -ServiceApplication My_Service_Application
]]>
        </Code>
        <Remarks> This example removes trusted locations from the Service application named, My_Service_Application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Clear-SPSecureStoreCredentialMapping </name>
    <synopsis><![CDATA[ Deletes a credential mapping from a Secure Store Service application. ]]></synopsis>
    <description><![CDATA[ The Clear-SPSecureStoreCredentialMapping cmdlet deletes a credential mapping from a Secure Store application ]]></description>
    <syntax>
      <![CDATA[
Clear-SPSecureStoreCredentialMapping -Identity <SPSecureStoreApplication> -Principal <SPClaim> [-AssignmentCollection <SPAssignmentColle
ction>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Clear-SPSecureStoreCredentialMapping -All <SwitchParameter> -Principal <SPClaim> -ServiceContext <SPServiceContextPipeBind> [-Assignment
Collection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApplication"
$userClaim = New-SPClaimsObject -User "CONTOSO\johndoe" -Type WindowsSamAccountName
Clear-SPSecureStoreCredentialMapping -Identity $ssApp -Principal $userClaim
]]>
        </Code>
        <Remarks>
          This example deletes the credential mapping from the target application ContosoTargetApplication for the user with alias johndoe
          and domain CONTOSO
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Clear-SPSecureStoreDefaultProvider </name>
    <synopsis><![CDATA[ Clears the secure store provider. ]]></synopsis>
    <description><![CDATA[ The Clear-SPSecureStoreDefaultProvider cmdlet clears the secure store provider ]]></description>
    <syntax>
      <![CDATA[
Clear-SPSecureStoreDefaultProvider [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Clear-SPSecureStoreDefaultProvider
]]>
        </Code>
        <Remarks> This example clears the secure store provider </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Clear-SPSiteSubscriptionBusinessDataCatalogConfig </name>
    <synopsis><![CDATA[ Deletes all data from the Business Data Connectivity Metadata Store for a specified partition. ]]></synopsis>
    <description>
      <![CDATA[ The Clear-SPSiteSubscriptionBusinessDataCatalogConfig cmdlet deletes all models and data from the Business Data Connectivity Meta
data Store for a specified service partition For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Clear-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentCollect
ion>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Clear-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext http://contoso
]]>
        </Code>
        <Remarks> This example deletes all data from the Business Data Connectivity Metadata Store for the specified site </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Connect-SPConfigurationDatabase </name>
    <synopsis><![CDATA[ Connects the local server computer to a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Connect-SPConfigurationDatabase cmdlet connects the current server to the specified configuration database Essentially, this cmdlet connects the server to the farm. If the current computer cannot be connected to a farm, the following er
ror message is displayed:} } "This machine is already connected to a SharePoint farm. See: Dismount-SPConfigurationDatabase"} } If the DatabaseName and Passphrase parameters are not specified, Windows authentication is used For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Connect-SPConfigurationDatabase [-DatabaseName] <String> [-Passphrase] <SecureString> -DatabaseServer <String> [-AssignmentCollection <S
PAssignmentCollection>] [-DatabaseCredentials <PSCredential>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Connect-SPConfigurationDatabase -DatabaseServer "ServerName\InstanceName" -DatabaseName "SharePointConfigurationDatabaseName" -Pas
sphrase (ConvertTo-SecureString "MyP@ssw0rd" -AsPlainText -Force 


C:\PS>Start-Service SPTimerv4
]]>
        </Code>
        <Remarks>
          This example joins the local server computer to a farm that is configured to use the database SharePointConfigurationDatabase on
          a SQL Server instance by using the name ServerName\InstanceName with the passphrase MyP@ssw0rd
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Copy-SPBusinessDataCatalogAclToChildren </name>
    <synopsis><![CDATA[ Copies a set of permissions of a Business Data Connectivity Metadata Store metadata object to its child objects. ]]></synopsis>
    <description>
      <![CDATA[ The Copy-SPBusinessDataCatalogAclToChildren cmdlet copies a set of rights of a Business Data Connectivity metadata object to its 
child objects Any principals and their rights will be lost from the child metadata objects. Make sure that the parent metadata object has the f
inal permissions you want, or make sure to append them to the child object again after you run this cmdlet Running this cmdlet on a BdcObjectType BdcCatalog (Business Data Connectivity Metadata Store) will propagate to:} } - BDC Models} } - External Systems} } - External Content Types} } - Methods} } - Method Instances} } Running this cmdlet on a BdcObjectType Model (Business Data Connectivity Model) will propagate to:} } - Nothing; this type has no child metadata objects} } Running this cmdlet on a BdcObjectType LobSystem (External System) will propagate to:} } - External Content Types} } - Methods} } - Method Instances} } Running this cmdlet on a BdcObjectType Entity (External Content Type) will propagate to:} } - Methods} } - Method Instances} } For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Copy-SPBusinessDataCatalogAclToChildren -MetadataObject <MetadataObject> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Sw
itchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ExternalSystem = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "LobSystem" -ServiceContext http://contoso -Name "Contoso
Database"
]]>
        </Code>
        <Remarks>
          This example looks at the principals (users) and their corresponding rights given for the External System metadata object, and ov
          erwrites the permissions of its child metadata objects with these same principals and rights Any principals and their rights will be lost from the child metadata objects. Make sure that the parent metadata object has the f
          inal permissions you want, or make sure to append them to the child object again after you run this cmdlet
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Disable-SPBusinessDataCatalogEntity </name>
    <synopsis><![CDATA[ Deactivates an External Content type in the Business Data Connectivity Metadata Store. ]]></synopsis>
    <description>
      <![CDATA[ The Disable-SPBusinessDataCatalogEntity cmdlet deactivates an External Content type in the Business Data Connectivity Metadata St
ore For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Disable-SPBusinessDataCatalogEntity -Identity <Entity> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [
-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$entityToDisable = Get-SPBusinessDataCatalogMetadataObject -Namespace "Contoso" -Name "Customer" -BdcObjectType "Entity" -ServiceC
ontext http://contoso
]]>
        </Code>
        <Remarks>
          This example deactivates the External Content type of the name Customer in the Contoso. Note that the terms External Content type
          and Entity refer to the same object type, and the term Disable refers to the same action as the Business Data Connectivity term Deactiva
          te
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Disable-SPFeature </name>
    <synopsis><![CDATA[ Disables an installed SharePoint Feature at a given scope. ]]></synopsis>
    <description>
      <![CDATA[ The Disable-SPFeature cmdlet disables a SharePoint Feature at the given scope. If the scope of the Feature is the farm, the URL i
s not needed. Otherwise, provide the URL at which this Feature is to be deactivated (explicit scope is not needed) For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Disable-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter
>]] [-Force <SwitchParameter>] [-Url <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Disable-SPFeature -identity "MyCustom" -URL http://somesite
]]>
        </Code>
        <Remarks> This example disables the "MyCustom" Web site scoped feature at   http://somesite </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>$w = Get-SPWeb http://somesite/myweb | ForEach{ $_.URL }

C:\PS>Get-SPFeature -Web $w |%{ Disable-SPFeature -Identity $_ -URL $w}
]]>
        </Code>
        <Remarks>
          This example disables all features in the subsite at http://somesite/myweb You do not need to use the SPAssignment cmdlets in this case because the Web object is not stored-- only the string value for the
          URL
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Disable-SPSessionStateService </name>
    <synopsis><![CDATA[ Turns off the session state service on the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Disable-SPSessionStateService cmdlet turns off the session state service. If your farm does not depend on session state servi
ce, we recommend that you disable it When session state is disabled, some Microsoft SharePoint Server 2010 services, components, and third-party components no longer 
function. Changing this property modifies the Web.config file on every content Web application on every server in the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Disable-SPSessionStateService [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter
>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Disable-SPSessionStateService
]]>
        </Code>
        <Remarks> This example turns off ASP.NET session state on the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Disable-SPSingleSignOn </name>
    <synopsis><![CDATA[ Disables the single sign-on (SSO) Service on a farm server. ]]></synopsis>
    <description><![CDATA[ Use the Disable-SPSingleSignOn cmdlet to disable the SSO Service on a farm server ]]></description>
    <syntax>
      <![CDATA[
Disable-SPSingleSignOn -ServerName <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<S
witchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Disable-SPSingleSignOn myOldSSO -ServerName CONTOSO
]]>
        </Code>
        <Remarks> This example turns off the SSO Service on the server named CONTOSO </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Disable-SPTimerJob </name>
    <synopsis><![CDATA[ Disables a timer job. ]]></synopsis>
    <description>
      <![CDATA[ The Disable-SPTimerJob cmdlet disables a timer job For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Disable-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Wh
atIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTimerJob job-ceip-datacollection | Disable-SPTimerJob
]]>
        </Code>
        <Remarks> This example disables the timer job named job-ceip-datacollection </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Disable-SPWebApplicationHttpThrottling </name>
    <synopsis><![CDATA[ Turns off network throttling for a Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Disable-SPWebApplicationHttpThrottling cmdlet turns off network throttling for a Web application. This operation prompts you 
to confirm that you want to turn off network throttling For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Disable-SPWebApplicationHttpThrottling [-Identity] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm
 [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Disable-SPWebApplicationHTTPThrottling http://sitename
]]>
        </Code>
        <Remarks> This example disables network throttling on the Web application http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Disconnect-SPConfigurationDatabase </name>
    <synopsis><![CDATA[ Disconnects the local server computer from the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Disconnect-SPConfigurationDatabase cmdlet disconnects the active server computer from the SharePoint configuration database. 
This operation removes the server computer from the farm. The configuration database must be disconnected before the database can be remo
ved For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Disconnect-SPConfigurationDatabase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchPara
meter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Disconnect-SPConfigurationDatabase -Confirm:$false
]]>
        </Code>
        <Remarks> This example removes the local server computer from a farm without prompting for user confirmation </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Dismount-SPContentDatabase </name>
    <synopsis><![CDATA[ Detaches a content database from its currently associated Web application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Dismount-SPContentDatabase cmdlet to detatch the given content database from its currently associated Web application. Th
is cmdlet will not delete the content database. Use the Remove-SPContentDatabase cmdlet to delete a content database For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Dismount-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1------------ </title>
        <Code>
          <![CDATA[
C:\PS>Dismount-SPContentDatabase 12345678-90ab-cdef-1234-567890abcdef
]]>
        </Code>
        <Remarks>
          This example detaches the content database with the GUID 12345678-90ab-cdef-1234-567890abcdef from its current parent Web applica
          tion
        </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDatabase -WebApplication http://sitename | Dismount-SPContentDatabase -WhatIf
]]>
        </Code>
        <Remarks>
          This example detaches all content databases from the Web application on port 80 of the local machine. Remove the WhatIf parameter
          to perform the operation
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Dismount-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Removes the association to a state service database from the farm without dropping the database in the Microsoft SQL Server database. ]]></synopsis>
    <description>
      <![CDATA[ The Dismount-SPStateServiceDatabase cmdlet removes a state service database from a service application and deletes the associated
 SharePoint object. This cmdlet does not delete or alter the state service database For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Dismount-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switc
hParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Dismount-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b
]]>
        </Code>
        <Remarks>
          This example removes the association between the SharePoint farm and the SQL Server database without dropping the SQL Server data
          base
        </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceDatabase -ServiceApplication F9168C5E-CEB2-4faa-B6B
F-329BF39FA1E4 | Dismount-SPStateServiceDatabase
]]>
        </Code>
        <Remarks> This example dismounts a single database because only the Identity parameter is used </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Enable-SPBusinessDataCatalogEntity </name>
    <synopsis><![CDATA[ Activates an External Content type in the Business Data Connectivity Metadata Store. ]]></synopsis>
    <description>
      <![CDATA[ The Enable-SPBusinessDataCatalogEntity cmdlet activates an External Content type in the Business Data Connectivity Metadata Store
 For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Enable-SPBusinessDataCatalogEntity -Identity <Entity> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-
WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$entityToEnable = Get-SPBusinessDataCatalogMetadataObject -Namespace "Contoso" -Name "Customer" -BdcObjectType "Entity" -ServiceCo
ntext http://contoso
Enable-SPBusinessDataCatalogEntity -Identity $entityToEnable
]]>
        </Code>
        <Remarks>
          This example activates the External Content type with the name Customer in the Contoso namespace on the site http://contoso. Note
          that the terms External Content type and Entity refer to the same object type
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Enable-SPFeature </name>
    <synopsis><![CDATA[ Enables an installed SharePoint Feature at the given scope. ]]></synopsis>
    <description>
      <![CDATA[ The Enable-SPFeature cmdlet enables an installed feature at the given scope.  If the feature is a farm feature, no URL is needed.
 Otherwise, provide the URL where the feature is to be enabled and it will be enabled at the proper scope based on the Feature definition
 This cmdlet has no output unless the PassThru parameter is provided, in which case the SPFeatureDefinition object for the newly e
nabled feature is returned If you try to use the Url parameter on a farm-scoped feature, you receive the following error message:} } The feature '<feature name>' applies to the entire farm; the Url parameter cannot be used with farm-scoped features For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Enable-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>
]] [-Force <SwitchParameter>] [-PassThru <SwitchParameter>] [-Url <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Enable-SPFeature -identity "MyCustom" -URL http://somesite
]]>
        </Code>
        <Remarks> This example enables the "MyCustom" site scoped SharePoint Feature at http://somesite </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>$w = Get-SPWeb http://somesite/myweb | ForEach{ $_.URL }

C:\PS>Get-SPFeature -Web $w |%{ Enable-SPFeature -Identity $_ -URL $w}
]]>
        </Code>
        <Remarks> This example enables all SharePoint Features in the subsite at http://somesite/myweb </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Enable-SPSessionStateService </name>
    <synopsis><![CDATA[ Creates a session state database and turns on the session state service. ]]></synopsis>
    <description>
      <![CDATA[ The Enable-SPSessionStateService cmdlet creates a session state database, installs the ASP.NET session state schema, and updates 
the Web.config files on the farm to turn on the session state service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Enable-SPSessionStateService -DatabaseName <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Da
tabaseCredentials <PSCredential>] [-DatabaseServer <String>] [-SessionTimeout <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParamete
rs>]
Enable-SPSessionStateService -DefaultProvision <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPara
meter>]] [-SessionTimeout <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Enable-SPSessionStateService -DefaultProvision
]]>
        </Code>
        <Remarks>
          This example enables a ASP.NET session state on a Microsoft SharePoint Server 2010 farm that uses the defaults (database hosted o
          n the configuration database SQL Server, using Windows authentication, 60-minute session time-out)
        </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Enable-SPSessionStateService -DatabaseName "Session State Database" -DatabaseServer "localhost" -SessionTimeout 120
]]>
        </Code>
        <Remarks>
          This example enables a ASP.NET session state on a Microsoft SharePoint Server 2010 farm that uses a custom database name, databas
          e server, session time-out of 120 minutes, and Windows credentials (due to the lack of a DatabaseCredentials parameter)
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Enable-SPTimerJob </name>
    <synopsis><![CDATA[ Enables a timer job. ]]></synopsis>
    <description>
      <![CDATA[ The Enable-SPTimerJob cmdlet enables a timer job. A timer job must be enabled before it can be started For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Enable-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Wha
tIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTimerJob job-ceip-datacollection | Enable-SPTimerJob
]]>
        </Code>
        <Remarks> This example enables the timer job named job-ceip-datacollection </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Enable-SPWebApplicationHttpThrottling </name>
    <synopsis><![CDATA[ Turns on network throttling for a Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Enable-SPWebApplicationHttpThrottling cmdlet turns on network throttling for a Web application. This operation prompts you to
 confirm that you want to turn on network throttling For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Enable-SPWebApplicationHttpThrottling [-Identity] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm 
[<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Enable-SPWebApplicationHttpThrottling http://sitename
]]>
        </Code>
        <Remarks> This example enables network throttling on the http://sitename Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Export-SPBusinessDataCatalogModel </name>
    <synopsis><![CDATA[ Exports a Business Data Connectivity Model. ]]></synopsis>
    <description>
      <![CDATA[ The Export-SPBusinessDataCatalogModel cmdlet exports a Business Data Connectivity Model.  There are two types of Business Data Co
nnectivity models: Model type (.bdcm) and Resource type (.bdcr). The Model type contains the base XML metadata, and can also include reso
urce properties. The Resource type includes only resource properties For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Export-SPBusinessDataCatalogModel -Identity <MetadataObject> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Force <Sw
itchParameter>] [-LocalizedNamesIncluded <SwitchParameter>] [-ModelsIncluded <SwitchParameter>] [-PermissionsIncluded <SwitchParameter>]
 [-PropertiesIncluded <SwitchParameter>] [-ProxiesIncluded <SwitchParameter>] [-SettingId <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$Model = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Model" -Name "ContosoModel" -ServiceConext http://contoso
Export-SPBusinessDataCatalogModel -Identity $Model -Path "C:\folder\model.bdcm"
]]>
        </Code>
        <Remarks>
          This example gets a Business Data Connectivity Model from the Business Data Connectivity Metadata Store and exports it to the loc
          ation specified with the name model and using the bdcm file extension
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Export-SPEnterpriseSearchTopology </name>
    <synopsis><![CDATA[ Saves an existing search topology. ]]></synopsis>
    <description>
      <![CDATA[ The Export-SPEnterpriseSearchTopology cmdlet exports the topology for a shared search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Export-SPEnterpriseSearchTopology -Filename <String> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAss
ignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceAplication
Export-SPEnterpriseSearchTopology -SearchApplication $ssa -Filename topology.xml
]]>
        </Code>
        <Remarks> This example exports the topology of a search service application to a file named topology.xml </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Export-SPInfoPathAdministrationFiles </name>
    <synopsis><![CDATA[ Saves Microsoft InfoPath 2010 form templates on the SharePoint Central Administration Web site and .udcx files to a .cab file. ]]></synopsis>
    <description>
      <![CDATA[ The Export-SPInfoPathAdministrationFiles cmdlet saves all InfoPath 2010 form templates (.xsn files) and universal data connection
s (.udcx files) that are located on the Central Administration page. The backup package includes all workflow forms in Microsoft InfoPath
 that were deployed by an administrator and not included with Microsoft SharePoint Server 2010, and includes browser forms that were depl
oyed by an administrator. The backup package is output to the specified .cab file For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Export-SPInfoPathAdministrationFiles -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Id
entity <SPFormsServicePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Export-SPInfoPathAdministrationFiles -path d:\file.cab
]]>
        </Code>
        <Remarks>
          This example saves all InfoPath 2010 form templates (.xsn files) and universal data connections (.udcx files) located on the Shar
          ePoint Central Administration Web site in a compressed cabinet file named file.cab
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Export-SPMetadataWebServicePartitionData </name>
    <synopsis><![CDATA[ Exports the data from a metadata Web service for a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ Use the Export-SPMetadataWebServicePartitionData cmdlet to export the data from a metadata Web service that is associated with th
e specified site subscription For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Export-SPMetadataWebServicePartitionData -Identity <SPSiteSubscriptionPipeBind> -ServiceProxy <SPMetadataServiceProxyCmdletPipeBind> -Pa
th <String> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Export-SPMetadataWebServicePartitionData -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -Path "\\serve
r_name\folder_name\file_name.cab"
]]>
        </Code>
        <Remarks> This example creates a backup of data for a specific site subscription on a Metadata Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Export-SPSiteSubscriptionBusinessDataCatalogConfig </name>
    <synopsis><![CDATA[ Exports all data from the Business Data Connectivity Metadata Store associated with a partition. ]]></synopsis>
    <description>
      <![CDATA[ The SPSiteSubscriptionBusinessDataCatalogConfig cmdlet exports all data from the Business Data Connectivity Metadata Store associ
ated with a specified partition For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Export-SPSiteSubscriptionBusinessDataCatalogConfig -Path <String> -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPA
ssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-LocalizedNamesIncluded <SwitchParameter>] [-ModelsIncl
uded <SwitchParameter>] [-PermissionsIncluded <SwitchParameter>] [-PropertiesIncluded <SwitchParameter>] [-ProxiesIncluded <SwitchParame
ter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Export-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext http://contoso -Path "C:\folder\exportedFile.xml"
]]>
        </Code>
        <Remarks> This example exports the data file named exportedFile.xml </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Export-SPSiteSubscriptionSettings </name>
    <synopsis><![CDATA[ Creates a backup file of site subscription data. ]]></synopsis>
    <description>
      <![CDATA[ The Export-SPSiteSubscriptionSettings cmdlet generates a backup file of all settings in the subscription data store for the given
 site subscription For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Export-SPSiteSubscriptionSettings [-Identity] <SPSiteSubscriptionPipeBind> -Path <String> [-AdminProperties <SwitchParameter>] [-Assignm
entCollection <SPAssignmentCollection>] [-Force <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscription http://contoso.com | Backup-SPSiteSubscriptionSettings -path "c:/backups"
]]>
        </Code>
        <Remarks> The example backs up the subscription settings store of http://www.contoso.com </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Export-SPWeb </name>
    <synopsis><![CDATA[ Exports a site collection, Web application, list, or library. ]]></synopsis>
    <description>
      <![CDATA[ The Export-SPWeb cmdlet exports a site collection, Web application, list, or library. The capability to export from a library is 
a new feature in SharePoint 2010 Products For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Export-SPWeb [-Identity] <SPWebPipeBind> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-CompressionSize <Int32>] [-Co
nfirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-HaltOnError <SwitchParameter>] [-HaltOnWarning <SwitchParameter>] [-IncludeUserS
ecurity <SwitchParameter>] [-IncludeVersions <LastMajor | CurrentVersion | LastMajorAndMinor | All>] [-ItemUrl <String>] [-NoFileCompres
sion <SwitchParameter>] [-NoLogFile <SwitchParameter>] [-UseSqlSnapshot <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParamet
ers>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE-----------------------. </title>
        <Code>
          <![CDATA[
C:\PS>Export-SPWeb http://site -Path "site export.cmp"
]]>
        </Code>
        <Remarks> This example exports the site at http://site/ to a file called site export.cmp in the current directory </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPAlternateURL </name>
    <synopsis><![CDATA[ Returns all alternate URLs that match a given set of criteria. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPAlternateURL cmdlet participates in a parameter set. The Get-SPAlternateURL cmdlet returns all alternate URLs that matc
h the scope given by either the optional Identity parameter or by a combination of the optional WebApplication, Zone, or Resource paramet
ers. Each criterion that is added narrows the scope. If no criteria are specified then all alternate URLs are returned If the Identity parameter is used, only the specific matching alternate URL is returned. If no alternate URL with the given ident
ity exists at the given scope, nothing is returned For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPAlternateURL [[-Identity] <SPAlternateUrlPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Zone <Default | Intranet | 
Internet | Custom | Extranet>] [<CommonParameters>]
Get-SPAlternateURL [[-Identity] <SPAlternateUrlPipeBind>] -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmen
tCollection>] [-Zone <Default | Intranet | Internet | Custom | Extranet>] [<CommonParameters>]
Get-SPAlternateURL [[-Identity] <SPAlternateUrlPipeBind>] -ResourceName <String> [-AssignmentCollection <SPAssignmentCollection>] [-Zone
 <Default | Intranet | Internet | Custom | Extranet>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPAlternateURL -WebApplication http://sitename
]]>
        </Code>
        <Remarks> This example displays all the alternate URLs on a given Web application </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPAlternateURL -ResourceName "MyResource"
]]>
        </Code>
        <Remarks> This example displays all the alternate URLs for a given resource </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPAuthenticationProvider </name>
    <synopsis><![CDATA[ Returns an authentication provider. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPAuthenticationProvider cmdlet returns an authentication provider on a specified Web application zone. The following are
 the standard authentication providers available for SharePoint 2010 Products: NTLM, Classic NTLM, Negotiate, and Classic Negotiate For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPAuthenticationProvider [[-Identity] <SPAuthenticationProviderPipeBind>] [-WebApplication] <SPWebApplicationPipeBind> [-Zone] <Defa
ult | Intranet | Internet | Custom | Extranet> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWebApplication http://sharepointonline.com -AuthenticationProvider (Get- SPAuthenticationProvider "LiveID STS")
]]>
        </Code>
        <Remarks> This example registers the LiveID STS authentication provider for the new Web application </Remarks>
      </example>
      <example>
        <title> -----------------EXAMPLE2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWebApplication http://contoso.com -AuthenticationProvider (New- SPAuthenticationProvider -ASPNetMembershipProvider "myMember
shipProvider" -ASPNetRoleProvider "myRoleProvider")
]]>
        </Code>
        <Remarks>
          This example registers ASPNet for the new Web application. Note that ASPNET memberships are not persisted and must be re-created
          every use
        </Remarks>
      </example>
      <example>
        <title> -----------------EXAMPLE3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWebApplication http://contoso.com -AuthenticationProvider (Get- SPAuthenticationProvider "NTLM")
]]>
        </Code>
        <Remarks>
          This example registers the NTLM authentication provider for the new Web application. This command is equivalent to the command Ne
          w-SPWebApplication http://contoso.com; NTLM is default authentication provider
        </Remarks>
      </example>
      <example>
        <title> -----------------EXAMPLE4----------------- </title>
        <Code>
          <![CDATA[
C:\PS>$ip = @( (Get- SPAuthenticationProvider "LiveID STS"), (New- SPAuthenticationProvider -ASPNetMembershipProvider "myMembershipProvi
der" -ASPNetRoleProvider "myRoleProvider"), (Get-SPAuthenticationProvider "NTLM")) )
New-SPWebApplication http://contoso.com -AuthenticationProvider $ip
]]>
        </Code>
        <Remarks> This example registers the NTLM, ASPNet, and LiveID STS authentication providers for the new Web application </Remarks>
      </example>
      <example>
        <title> -----------------EXAMPLE5----------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWebApplication http://contoso.com -AuthenticationProvider (Get- SPAuthenticationProvider "Legacy NTLM")
]]>
        </Code>
        <Remarks> This example registers the Legacy NTLM authentication provider for the new Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPBackupHistory </name>
    <synopsis><![CDATA[ Returns a history of backup and restore operations. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPBackupHistory cmdlet reads a history of backup and restore operations that have been run. Specifies whether you want to
 display only the backup history, only the restore history, or all of the history For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPBackupHistory -Directory <String> [-AssignmentCollection <SPAssignmentCollection>] [-ShowBackup <SwitchParameter>] [-ShowRestore <
SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPBackupHistory -Directory \\file_server\share\Backup
]]>
        </Code>
        <Remarks> This example returns all farm backup and restore operations that have been run for the \\file_server\share\Backup directory </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPBackupHistory -Directory C:\Backup -ShowBackup
]]>
        </Code>
        <Remarks> This example returns all of the farm backup operations that have been run for the C:\Backup directory </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>(Get-SPBackupHistory -Directory C:\Backup -ShowBackup)[0].SelfId | Restore-SPFarm -Directory C:\Backup -RestoreMethod overwrite
]]>
        </Code>
        <Remarks>
          This example gets all of the farm backup operations that have been run for the C:\Backup directory, finds the most recent backup,
          and then passes its backup GUID to the Restore-SPFarm cmdlet. The Restore-SPFarm cmdlet will then perform an overwrite restore from that
          backup package
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPBrowserCustomerExperienceImprovementProgram </name>
    <synopsis><![CDATA[ Returns the current opt-in state for the browser Customer Experience Improvement Program. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPBrowserCustomerExperienceImprovementProgram cmdlet reads the current opt-in state for the browser Customer Experience I
mprovement Program For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPBrowserCustomerExperienceImprovementProgram -Farm <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParam
eters>]
Get-SPBrowserCustomerExperienceImprovementProgram -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollect
ion>] [<CommonParameters>]
Get-SPBrowserCustomerExperienceImprovementProgram -SiteSubscription <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCol
lection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPBrowserCustomerExperienceImprovementProgram -WebApplication http://WebAppexample1
]]>
        </Code>
        <Remarks> This example returns the current Customer Experience Improvement Program opt-in state for the Web application, WebAppexample1 </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscription http://SiteSubscription1 | Get- SPBrowserCustomerExperienceImprovementProgram
]]>
        </Code>
        <Remarks>
          The following example returns the Customer Experience Improvement Program opt-in state for the site subscription, SiteSubscriptio
          n1
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPBusinessDataCatalogMetadataObject </name>
    <synopsis><![CDATA[ Returns a Business Data Connectivity Metadata Store metadata object. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPBusinessDataCatalogMetadataObject cmdlet reads a Business Data Connectivity Metadata Store metadata object from a Busin
ess Data Connectivity Service application. Output for this cmdlet can be a series of objects. For example, you can specify a wildcard cha
racter (*) for the BdcObjectType parameter to return all metadata objects except Catalog and LobSystemInstance For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPBusinessDataCatalogMetadataObject -BdcObjectType <Catalog | Model | LobSystem | LobSystemInstance | Entity> -ServiceContext <SPSer
viceContextPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-ContainingLobSystem <String>] [-Name <String>] [-Namespace <Stri
ng>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$Model = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Model" -Name "ContosoModel" -ServiceConext http://contoso
]]>
        </Code>
        <Remarks>
          This example gets a metadata object of type Model with the name ContosoModel from the Business Data Connectivity Metadata Store o
          n the given site
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPBusinessDataCatalogThrottleConfig </name>
    <synopsis><![CDATA[ Returns the throttling configuration for a Business Data Connectivity Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPBusinessDataCatalogThrottleConfig cmdlet reads the throttling configuration for a Business Data Connectivity Service ap
plication For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPBusinessDataCatalogThrottleConfig -Scope <Global | Database | WebService | Wcf | Custom> -ServiceApplicationProxy <SPServiceApplic
ationProxyPipeBind> -ThrottleType <None | Items | Size | Connections | Timeout> [-AssignmentCollection <SPAssignmentCollection>] [<Commo
nParameters>]
Get-SPBusinessDataCatalogThrottleConfig -FileBacked <SwitchParameter> -Scope <Global | Database | WebService | Wcf | Custom> -ThrottleTy
pe <None | Items | Size | Connections | Timeout> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottleType Items -ServiceApplicationProxy $contosoServAppProxy
]]>
        </Code>
        <Remarks> This example returns the throttling information that is related to database items for the given service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPCertificateAuthority </name>
    <synopsis><![CDATA[ Returns the SharePoint certificate authority (CA). ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPCertificateAuthority cmdlet returns the SharePoint certificate authority (CA) For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPCertificateAuthority [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$signingCert = (Get-SPServiceApplication | where $_.Name -eq 'SecurityTokenServiceApplication').SigningCertificate
]]>
        </Code>
        <Remarks> This example gets the security token service (STS) identity provider signing certificate </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPClaimProvider </name>
    <synopsis><![CDATA[ Returns a claim provider. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPClaimProvider cmdlet returns a claim provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPClaimProvider [[-Identity] <SPClaimProviderPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get - SPClaimProvider -Identity "MyClaimProvider" | Set-SPClaimProvider -Enabled $false
]]>
        </Code>
        <Remarks> This example disables the claim provider MyClaimProvider </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPClaimProviderManager </name>
    <synopsis><![CDATA[ Returns a claim provider manager. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPClaimProviderManager cmdlet reads a claim provider manager For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPClaimProviderManager [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> Add code example. </title>
        <Code>
          <![CDATA[
C:\PS>
]]>
        </Code>
        <Remarks>  </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPContentDatabase </name>
    <synopsis><![CDATA[ Returns one or more content databases. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPContentDatabase cmdlet returns the specified content databases For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPContentDatabase [[-Identity] <SPContentDatabasePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
Get-SPContentDatabase -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
Get-SPContentDatabase -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
Get-SPContentDatabase -ConnectAsUnattachedDatabase <SwitchParameter> -DatabaseName <String> -DatabaseServer <String> [-AssignmentCollect
ion <SPAssignmentCollection>] [-DatabaseCredentials <PSCredential>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE 1------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDatabase -webapplication http://sitename
]]>
        </Code>
        <Remarks> This example returns all content databases used by the sitename Web application </Remarks>
      </example>
      <example>
        <title> ----------------EXAMPLE 2------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDatabase -site http://contoso.com
]]>
        </Code>
        <Remarks> This example returns the content database that contains the site collection at http://contoso.com </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPContentDeploymentJob </name>
    <synopsis>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Get-SPContentDeploymentJob [[-Identity] <SPContentDeploymentJobPipeBind>] [-Path <SPContentDeploymentPathPipeBind>] [-AssignmentCollecti
on <SPAssignmentCollection>] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <
String>] [-WarningVariable <String>] [-OutVariable <String>] [-OutBuffer <Int32>]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPContentDeploymentPath </name>
    <synopsis>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Get-SPContentDeploymentPath [[-Identity] <SPContentDeploymentPathPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Verbose] 
[-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>] [-O
utVariable <String>] [-OutBuffer <Int32>]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPCustomLayoutsPage </name>
    <synopsis><![CDATA[ Returns a mapping to a custom layout page. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPCustomLayoutsPagecmdlet cmdlet returns a mapping to a custom layout page in a Web application. If the Identity paramete
r is not specified, this cmdlet returns the collection of mappings for all custom layout pages For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPCustomLayoutsPage -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Identity <None | A
ccessDenied | Confirmation | Error | Login | RequestAccess | Signout | WebDeleted>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPCustomLayoutsPage -Identity "_layouts/accessdenied.aspx" -WebApplication "http://server_name/mywebapp"
]]>
        </Code>
        <Remarks> This example returns the mapping of the AccessDenied layout page in the Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPDatabase </name>
    <synopsis><![CDATA[ Retrieves all properties of a database. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPDatabase cmdlet displays all public properties of a database to the current window. If the Identity parameter is specif
ied, only properties of that ID are displayed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185 ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPDatabase [[-Identity] <SPDatabasePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
Get-SPDatabase -ServerInstance <SPDatabaseServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDatabase -ServerInstance "ServerA\SharePoint"
]]>
        </Code>
        <Remarks> This example gets all databases on a specific named SQL Server Express instance </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPDataConnectionFile </name>
    <synopsis><![CDATA[ Returns a data connection file or a collection of data connection files. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPDataConnectionFile cmdlet gets a specified data connection file or a collection of data connection files. If the Identi
ty parameter is not specified, the cmdlet returns the collection of data connection files for the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPDataConnectionFile [-Identity <SPDataConnectionFilePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>
]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE 1-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDataConnectionFile
]]>
        </Code>
        <Remarks> This example lists the Identity, DisplayName, and WebAccessible properties ofeach .udcx file </Remarks>
      </example>
      <example>
        <title> ---------------EXAMPLE 2-------------- </title>
        <Code>
          <![CDATA[
C:\PS>"Sample.udcx" | Get-SPDataConnectionFile
]]>
        </Code>
        <Remarks> This example lists the Identity, DisplayName, and WebAccessible properties of the specified file, named Sample.udcx </Remarks>
      </example>
      <example>
        <title> ---------------EXAMPLE 3-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDataConnectionFile | where {$_.Category -eq "Category1"}
]]>
        </Code>
        <Remarks> This example lists the Identity, DisplayName, and WebAccessible properties of all .udcx files with the specified Category </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPDataConnectionFileDependent </name>
    <synopsis><![CDATA[ Returns deployed forms on the server dependent on a universal data connection. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPDataConnectionFileDependent returns all administrator deployed forms that depend on a specified universal data connecti
on (.udc) file located in the central data connection store For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPDataConnectionFileDependent -Identity <SPDataConnectionFilePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonPara
meters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDataConnectionFileDependant -Identity "FileName.udcx

C:\PS>"FileName.udcx" | Get-SPDataConnectionFileDependant
]]>
        </Code>
        <Remarks> This example displays a list of deployed forms with a specified name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPDesignerSettings </name>
    <synopsis><![CDATA[ Displays Microsoft SharePoint Designer 2010 features. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPDesignerSettings cmdlet determines whether SharePoint Designer 2010 features are enabled on the specified Web applicati
on For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPDesignerSettings [-WebApplication] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>
]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDesignerSettings -webapplication http://contoso
]]>
        </Code>
        <Remarks> This example retrieves the SharePoint Designer 2010 settings for the Web application, http://contoso </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPDiagnosticConfig </name>
    <synopsis><![CDATA[ Retrieves ULS diagnostic configuration values of the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPDiagnoticConfig cmdlet retrieves ULS diagnostic configuation values of the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPDiagnosticConfig [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDiagnosticConfig
]]>
        </Code>
        <Remarks> This example returns all diagnostic configuration values </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPDiagnosticsPerformanceCounter </name>
    <synopsis><![CDATA[ Returns a collection of performance counters. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPDiagnosticsPerformanceCounter cmdlet returns the collection of performance counters that are read and recorded in the U
sage Database. If the neither the DatabaseServer or WebFrontEnd parameters are specified, this cmdlet returns the performance counters on
 the Web front end computes on a database servers in the farm To distinguish counters that are collected on database servers and counters that are collected on Web front end computers, note t
hat counters that are collected on database servers have a Provider Name of job-diagnostics-performance-counter-sql-provider, and counter
s that are collected on Web front end computers have a Provider Name of job-diagnostics-performance-counter-wfe-provider The Get-SPDiagnosticsPerformanceCounter cmdlet is only available using Windows PowerShell. There is no User Interface For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPDiagnosticsPerformanceCounter [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseServer <SwitchParameter>] [-WebFrontEnd <
SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get- SPDiagnosticsPerformanceCounter
]]>
        </Code>
        <Remarks> This example gets the performance counter settings for Web front end computers and database servers </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get- SPDiagnosticsPerformanceCounter -WebFrontEnd
]]>
        </Code>
        <Remarks> This example gets the performance counter settings for Web front end computers </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get- SPDiagnosticsPerformanceCounter -DatabaseServer
]]>
        </Code>
        <Remarks> This example gets the performance counter settings for database servers </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPDiagnosticsProvider </name>
    <synopsis><![CDATA[ Returns a diagnostics provider. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPDiagnosticsProvider cmdlet reads the specified diagnostics provider. If the Identity parameter is not specified, this c
mdlet returns the collection diagnostics providers in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPDiagnosticsProvider [[-Identity] <SPDiagnosticsProviderPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParamet
ers>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDiagnosticsProvider
]]>
        </Code>
        <Remarks> This example returns all the diagnostics providers in the farm </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDiagnosticsProvider job-diagnostics-event-log-provider
]]>
        </Code>
        <Remarks> This example returns the event log diagnostics provider </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchAdministrationComponent </name>
    <synopsis><![CDATA[ Returns the administration component for a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchAdmininstrationComponent cmdlet retrieves an administration component for a search service application 
in order to update or delete it For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchAdministrationComponent -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignment
Collection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication ExampleSearchServiceApplication
$adminCmpnt = Get-SPEnterpriseSearchAdministrationComponent
  -SearchApplication $searchApp
]]>
        </Code>
        <Remarks>
          This example obtains an object reference to the administration component of a search service application named ExampleSearchServi
          ceApplication
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlComponent </name>
    <synopsis><![CDATA[ Returns a crawl component for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchCrawlComponent cmdlet reads a CrawlComponent object when a crawl component for a shared search applicat
ion is created, updated, or deleted. If the Identity parameter is not specified, this cmdlet returns the crawl component collection for t
he specified crawl topology For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlComponent [[-Identity] <CrawlComponentPipeBind>] -CrawlTopology <CrawlTopologyPipeBind> [-AssignmentCollectio
n <SPAssignmentCollection>] [-SearchApplication <SearchServiceApplicationPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceApplication "SearchApp1" | Get-SPEnterpriseSearchCrawlTopology -Active | Get-SPEnterpriseSearchCrawlC
omponent
]]>
        </Code>
        <Remarks> This example retrieves the list of all crawl components in the active crawl topology for the search application SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlContentSource </name>
    <synopsis><![CDATA[ Returns a crawl content source. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchCrawlContentSource cmdlet reads the content source when the rules of content source are created, update
d, or deleted, or reads a CrawlContentSource object when the search functionality is initially configured and after any new content sourc
e is added If the Identity parameter is not specified, this cmdlet returns the content source collection for the specified search applicatio
n For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlContentSource [[-Identity] <ContentSourcePipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-A
ssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication " SearchApp1" 
$contentsource = Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $searchapp -Identity "Local SharePoint Sites" $contentsourc
e.StartFullCrawl()
]]>
        </Code>
        <Remarks>
          This example retrieves the default content source for the search service application, SearchApp1, and starts a full crawl on the
          content source
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlCustomConnector </name>
    <synopsis><![CDATA[ Returns a CustomConnector object type. ]]></synopsis>
    <description>
      <![CDATA[ The Identity parameter displays a custom connector for a specified Web application. If no parameters are specified, all the objec
ts of the CustomConnector object type are returned For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlCustomConnector -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCol
lection>] [-Protocol <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication MySearchServiceApp
$crawlConn = Get-SPEnterpriseSearchCrawlCustomConnector -SearchApplication
$searchApp -Protocol "http://"
]]>
        </Code>
        <Remarks>
          This example obtains a reference to all custom crawl connectors for the http:// protocol for a search service application named M
          ySearchServiceApp
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlDatabase </name>
    <synopsis><![CDATA[ Returns a crawl store. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchCrawlDatabase cmdlet returns a CrawlStore object for use during configuration and when a crawl database
 for a search service application is modified or deleted. A crawl database stores crawl history data for a search service application If the Identity parameter is not specified, this cmdlet returns the crawl database collection for the specified search applicatio
n For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlDatabase [[-Identity] <CrawlStorePipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Assignmen
tCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>
$crawlDatabase = Get-SPEnterpriseSearchCrawlDatabase -SearchApplication
MySearchServiceApp -Identity CrawlDB_1
]]>
        </Code>
        <Remarks> This example gets a reference to the crawl database CrawlDB_1 from the search service application named MySearchServiceApp </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlExtension </name>
    <synopsis><![CDATA[ Returns the file types to be included in the content index. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchCrawlExtension cmdlet returns any or all file extensions in the index for a search application Run this cmdlet at the initial search configuration, and after any new IFilter interface is added to read the rule when you creat
e, update, or delete the extension rule. If the Identity parameter is not specified, this cmdlet returns the crawl extension collection f
or the specified search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlExtension [[-Identity] <ExtensionPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Assignmen
tCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> Add code example. </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "Sample Search Service Application"
$searchapp | Get-SPEnterpriseSearchCrawlExtension "pdf"
]]>
        </Code>
        <Remarks> This example checks whether the pdf file type is included in the file types to be included in the content index </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlMapping </name>
    <synopsis><![CDATA[ Returns a crawl mapping for the search application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchCrawlMapping cmdlet reads a CrawlMapping object when one of the crawl mapping rules is created, updated
, or deleted. Run this cmdlet when the search is initially configured, and when access is changed through a different mechanism to create
 the crawl mapping rule; for example, when a rule is changed to use file:\\ rather than http:// If the Identity parameter is not specified, this cmdlet returns the crawl mapping collection for the specified search application
 For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlMapping [[-Identity] <CrawlMappingPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Assignme
ntCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title>  </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$searchapp | Get-SPEnterpriseSearchCrawlMapping
]]>
        </Code>
        <Remarks> This example returns the crawl mappings for the search application SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlRule </name>
    <synopsis><![CDATA[ Accesses crawl rules. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPEnterpriseSearchCrawlRule cmdlet for a search administrator to run this procedure to retrieve the crawl rule when t
he crawl rule is updated or deleted For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlRule [[-Identity] <CrawlRulePipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentColl
ection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication ExampleSearchServiceApplication 
$crawlRule = Get-SPEnterpriseSearchCrawlRule -SearchApplication  $searchApp -Identity http://example
$crawlRule | Set-SPEnterpriseSearchCrawlRule -Type InclusionRule
]]>
        </Code>
        <Remarks>
          This example uses the Get-SPEnterpriseSearchCrawlRule cmdlet to retrieve a crawl rule in order to change its type from ExclusionR
          ule to InclusionRule
        </Remarks>
      </example>
      <example>
        <title> ---------------EXAMPLE 2--------------- </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication MySearchServiceApp Get-SPEnterpriseSearchCrawlRule -SearchApplication $searc
hApp | where 
{$_.Path -like "*example*"}
]]>
        </Code>
        <Remarks>
          This example returns a list of crawl rules with paths that contain the word example from the search service application named, My
          SearchServiceApp
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchCrawlTopology </name>
    <synopsis><![CDATA[ Returns a crawl topology. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchCrawlTopology cmdlet returns a crawl topology for a search application. A crawl topology contains the c
rawl component collection for a topology If the Identity parameter is not specified, this cmdlet returns the crawl topology collection for the specified search applicatio
n For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchCrawlTopology [[-Identity] <CrawlTopologyPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Active
 <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" 
$searchapp | Get-SPEnterpriseSearchCrawlTopology
]]>
        </Code>
        <Remarks> This example returns all crawl topologies for the search application SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchIndexPartition </name>
    <synopsis><![CDATA[ Returns an index partition for a query topology. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchIndexPartition cmdlet returns an index partition for a query topology. Index partitions define how docu
ment IDs are mapped to the query components for full-text user queries for a shared search application If the Identity parameter is not specified, this cmdlet returns the index partition collection for the specified query topology For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchIndexPartition [[-Identity] <IndexPartitionPipeBind>] -QueryTopology <QueryTopologyPipeBind> [-AssignmentCollectio
n <SPAssignmentCollection>] [-SearchApplication <SearchServiceApplicationPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title>  </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" 
$qtopo = Get-SPEnterpriseSearchQueryTopology -SearchApplication $searchapp
$index = Get-SPEnterpriseSearchIndexPartition -QueryTopology $qtopo
]]>
        </Code>
        <Remarks> This example retrieves an index partition for the only query topology in the search service application SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchLanguageResourcePhrase </name>
    <synopsis><![CDATA[ Returns a language resource phrase. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchLanguageResourcePhrase cmdlet reads a LanguageResourcePhrase object when the language resource phrase i
s created or deleted For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchLanguageResourcePhrase [[-Identity] <LanguageResourcePhrasePipeBind>] -SearchApplication <SearchServiceApplication
PipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Language <String>] [-Mapping <String>] [-Type <Nullable>] [<CommonParameter
s>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" 
Get-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $searchapp -Language en-us -Type QuerySuggestionBlockList
]]>
        </Code>
        <Remarks> This example returns all language resource entries for the en-us language in the QuerySuggestionBlockList type </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchMetadataCategory </name>
    <synopsis><![CDATA[ Returns a crawled property category. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchMetadataCategory cmdlet reads a MetadataCategory object when the category is created, updated, or delet
ed. Run this cmdlet when the initial search is configured and after a new crawled property category is discovered during a crawl. SPEnter
priseSearchMetadataCategory represents a category in the enterprise search metadata property schema If the Identity parameter is not specified, this cmdlet returns the metadata category collection for the specified search applica
tion For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchMetadataCategory [[-Identity] <CategoryPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Assignme
ntCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" 
$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $searchapp -Identity People
]]>
        </Code>
        <Remarks> This example returns the People metadata category for the search application SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchMetadataCrawledProperty </name>
    <synopsis><![CDATA[ Returns a crawled property. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchMetadataCrawledProperty cmdlet reads a CrawledProperty object when the crawled category is created, upd
ated, or deleted. Run this cmdlet when the search functionality is initially configured and after new crawled properties are discovered d
uring a crawl. If the Name parameter is not specified, this cmdlet returns all crawled properties for the specified category for the spec
ified search application. If neither the Name nor the Category parameter is specified, this cmdlet returns all crawled properties for the
 specified search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchMetadataCrawledProperty [[-Name] <String>] -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentColle
ction <SPAssignmentCollection>] [-Category <CategoryPipeBind>] [-Limit <String>] [-PropSet <Nullable>] [-VariantType <Nullable>] [<Commo
nParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" 
$cat = Get-SPEnterpriseSearchMetadataCategory -SearchApplication $searchapp -Identity People
Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Category $cat
]]>
        </Code>
        <Remarks> This example returns all crawled properties for the search application SearchApp1 in the People metadata category </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchMetadataManagedProperty </name>
    <synopsis><![CDATA[ Returns a managed property. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchMetadataManagedProperty cmdlet reads a ManagedProperty object when managed properties are created, upda
ted, or deleted If the Identity parameter is not specified, this cmdlet returns the managed property collection for the specified search applicat
ion For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchMetadataManagedProperty [[-Identity] <ManagedPropertyPipeBind>] -SearchApplication <SearchServiceApplicationPipeBi
nd> [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity testmanagedproperty
]]>
        </Code>
        <Remarks> This example returns the managed property named testmanagedproperty for the search application SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchMetadataMapping </name>
    <synopsis><![CDATA[ Returns the current state of a managed property mapping. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchMetadataMapping cmdlet reads a Mapping object when the managed property mapping is created, updated, or
 deleted. SPEnterpriseSearchMetadataMapping represents a category of a mapping between a managed property and one or more crawled propert
ies in the enterprise search metadata property schema If the Identity parameter is not specified, this cmdlet returns the metadata mapping collection for the specified search applicat
ion For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchMetadataMapping -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollecti
on>] [-CrawledProperty <CrawledPropertyPipeBind>] [-ManagedProperty <ManagedPropertyPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "Sample Search Service Application"
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity Author
Get-SPEnterpriseSearchMetadataMapping -SearchApplication $searchapp -ManagedProperty $mp
]]>
        </Code>
        <Remarks> This example lists all crawled properties mapped to the Author managed property </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchPropertyDatabase </name>
    <synopsis><![CDATA[ Returns a property store. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchPropertyDatabase cmdlet reads a PropertyStore object for a search service application when the property
 store is created or updated. The PropertyStore object stores metadata about content for a search service application If the Identity parameter is not specified, this cmdlet returns the property store collection for the specified search applicatio
n For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchPropertyDatabase [[-Identity] <PropertyStorePipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Ass
ignmentCollection <SPAssignmentCollection>] [-IndexPartition <IndexPartitionPipeBind>] [-QueryTopology <QueryTopologyPipeBind>] [<Common
Parameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>$propertyDB = Get-SPEnterpriseSearchPropertyDatabase -SearchApplication 
mySearchServiceApp -Identity ExamplePropertyDB
]]>
        </Code>
        <Remarks> This example obtains a reference to the property database ExamplePropertyDB from the mySearchServiceApp search application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryAndSiteSettingsService </name>
    <synopsis><![CDATA[ Returns the search manager service. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryAndSiteSettingsService cmdlet returns a manager service. A manager service is the endpoint for the
 search service application to process queries and site administration requests from the search service application proxy For permissions and the most current information about search cmdlets, see the online documentation (http://go.microsoft.com/fwli
nk/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryAndSiteSettingsService [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$qssService = Get-SPEnterpriseSearchQUeryAndSiteSettingsService
]]>
        </Code>
        <Remarks> This example obtains a reference to the query and site settings service </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance </name>
    <synopsis><![CDATA[ Returns the service manager service instance. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance cmdlet returns the service manager service instance when a search m
anager service is started or stopped For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance [[-Identity] <SearchQueryAndSiteSettingsServiceInstancePipeBind>] [-Assignment
Collection <SPAssignmentCollection>] [-Local <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$qqssSvcInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local
]]>
        </Code>
        <Remarks> This example obtain a reference to the query and site setting service instance on the local farm </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$qssSvcInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity myServer
]]>
        </Code>
        <Remarks> This example obtain a reference to the query and site setting service instance from a specific server name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy </name>
    <synopsis><![CDATA[ Returns the search manager service proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy cmdlet reads the SearchQueryAndSiteSettingsServiceProxy object when a 
search Web service manager service is started or stopped For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$qssSvcProxy = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceProxy
]]>
        </Code>
        <Remarks> This example obtains a reference to the query and site settings service proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryAuthority </name>
    <synopsis><![CDATA[ Returns an authoritative page. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryAuthority cmdlet reads a QueryAuthority object when the authoritative page is created or deleted o
r when the query rank is modified If the Identity parameter is not specified, this cmdlet returns the authority page collection for the specified search applicatio
n For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryAuthority [[-Identity] <AuthorityPagePipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Assig
nmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA"
$qAuth = $ssa | Get-SPEnterpriseSearchQueryAuthority -Identity "http://contoso.com"
]]>
        </Code>
        <Remarks> This example obtains the authoritative page for the URL http://contoso.com from the search service application named MySSA </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$qaCollection = Get-SPEnterpriseSearchQueryAuthority -SearchApplication "MySSA"
]]>
        </Code>
        <Remarks> This example obtains the collection of query authority pages from a search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryComponent </name>
    <synopsis><![CDATA[ Returns a query component. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryComponent cmdlet reads a QueryComponent object when the query component is created, updated, or de
leted If the Identity parameter is not specified, this cmdlet returns the query component collection from the specified query topology.
} } For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryComponent [[-Identity] <QueryComponentPipeBind>] -QueryTopology <QueryTopologyPipeBind> [-AssignmentCollectio
n <SPAssignmentCollection>] [-SearchApplication <SearchServiceApplicationPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa =  Get-SPEnterpriseSearchServiceApplication -Identity "MySSA"
$ssa | Get-SPEnterpriseSearchQueryTopology -Active | Get-SPEnterpriseSearchQueryComponent
]]>
        </Code>
        <Remarks> This example gets the collection of query components from the search application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryDemoted </name>
    <synopsis><![CDATA[ Returns a demoted site rule. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryDemoted cmdlet reads the DemotedSite object when a demoted site rule is created or deleted, or whe
n the demoted site rule is updated to modify the query rank If the Identity parameter is not specified, this cmdlet returns the demoted site rule collection for the specified search applica
tion For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryDemoted [[-Identity] <DemotedPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCol
lection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$demotedRule = Get-SPEnterpriseSearchQueryDemoted -Identity http://somesite.com -SearchApplication MySSA
$demotedRule | Remove-SPEnterpriseSearchQueryDemoted
]]>
        </Code>
        <Remarks> This example obtains a reference to a site demotion rule for the URL http://somesite.com, and removes it </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryKeyword </name>
    <synopsis><![CDATA[ Returns a keyword term. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryKeyword cmdlet reads a QueryKeyword object when the keyword rule is created, updated, or deleted If the Identity parameter is not specified, this cmdlet returns the query keyword collection from the specified search applicatio
n For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryKeyword [[-Identity] <KeywordPipeBind>] -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection
>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchQueryKeyword -Identity Engineering -Site http://myserver/sites/engineering | Set-SPEnterpriseSearchQueryKeyw
ord -StartDate "12/25/2009" -EndDate "12/24/2010" -Site http://myserver/sites/engineering
]]>
        </Code>
        <Remarks>
          This example gets a reference to the keyword with the term Engineering from the site http://myserver/sites/engineering and sets t
          he start dates and end dates for the keyword
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryScope </name>
    <synopsis><![CDATA[ Returns a query results scope. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryScope cmdlet reads a QueryScope object when the shared scope is created or deleted, or when the de
finition of the shared scope is updated If the Identity parameter is not specified, this cmdlet returns the query scope collection from the specified search application.
} } For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryScope [[-Identity] <ScopePipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollect
ion <SPAssignmentCollection>] [-Url <Uri>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPenterpriseSearchServiceApplication -Identity MySSA
Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa | Set-SPEnterpriseSearchQueryScope -Description "Business c
ritical sites to index" -CompilationType 1 -AlternateResultsPage http://altServer
]]>
        </Code>
        <Remarks>
          This example obtains a reference to the scope named MustCrawl on the search application named MySSA, and changes the description,
          compilation type, and alternate access URL
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryScopeRule </name>
    <synopsis><![CDATA[ Returns a shared scope rule. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryScopeRule cmdlet reads a QueryScopeRule object when the shared scope rule is created, updated, or 
deleted. SPEnterpriseSearchQueryScopeRule represents a query result scope rule that can be applied to a scope For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryScopeRule [[-Identity] <ScopeRulePipeBind>] -Scope <ScopePipeBind> [-AssignmentCollection <SPAssignmentCollec
tion>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-Url <Uri>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA"
$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa
Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url http://criticalSite | Set-SPEnterpriseSearchQueryScopeRule -Url http://criticalS
ite -UrlScopeRuleType Url
]]>
        </Code>
        <Remarks> This example gets a reference to a scope rule for the URL http://criticalSite, and sets its rule type to URL </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQuerySuggestionCandidates </name>
    <synopsis><![CDATA[ Returns a list of queries. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPEnterpriseSearchQuerySuggestionCandidates cmdlet to return a list of popular queries that can be displayed in a rel
ated queries Web Part. The list gives the administrator a chance to review potential queries and add some of them to the related queries 
list For permissions and the most current information about search cmdlets, see the online documentation (http://go.microsoft.com/fwli
nk/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQuerySuggestionCandidates -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignme
ntCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication

C:\PS>Get-SPEnterpriseSearchQuerySuggestionCandidates -SearchApplication $searchapp
]]>
        </Code>
        <Remarks> This example returns popular search queries by using the search application contained in the variable $searchapp </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchQueryTopology </name>
    <synopsis><![CDATA[ Returns a query topology. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchQueryTopology cmdlet reads a QueryTopology object when the query topology is created, updated, or delet
ed If the Identity parameter is not specified, this cmdlet returns the query topology collection from a farm for the specified searc
h application For permissions and the most current information about search cmdlets, see the online documentation (http://go.microsoft.com/fwli
nk/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchQueryTopology [[-Identity] <QueryTopologyPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Active
 <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$queryTopology$searchapp = Get-SPEnterpriseSearchServiceApplication -"SearchApp1" 
$qtopo = Get-SPEnterpriseSearchQueryTopology -SearchApplication MySSA$searchapp -Active
]]>
        </Code>
        <Remarks> This example retrieves the active query topology from a search application named SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchRankingModel </name>
    <synopsis><![CDATA[ Returns a ranking model. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchRankingModel cmdlet reads the RankingModel object when a ranking model is created, removed, or updated.
} } If the Identity parameter is not specified or the identity does not match any of the ranking models in the collection, an excepti
on is thrown and the default ranking model is used For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchRankingModel [[-Identity] <RankingModelPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-Assignme
ntCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$rankingModelList = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA" | Get-SPEnterpriseSearchRankingModel
]]>
        </Code>
        <Remarks> This example obtains a reference to the collection of ranking models for the search service application MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchSecurityTrimmer </name>
    <synopsis><![CDATA[ Returns a custom security trimmer. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchSecurityTrimmer cmdlet returns the PluggableSecurityTrimmer object when a customized security trimmer i
s created, updated, or deleted for the query results of the specified search application. A custom security trimmer trims search results 
before the results are returned to the user If the Identity parameter is not specified, this cmdlet returns the security trimmer collection for the specified search applicat
ion For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchSecurityTrimmer [[-Identity] <SecurityTrimmerPipeBind>] -SearchApplication <SearchServiceApplicationPipeBind> [-As
signmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceApplication -Identity MySSA | Get-SPEnterpriseSearchSecurityTrimmer
]]>
        </Code>
        <Remarks> This example obtains the pluggable security trimmers registered in the search service application MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchService </name>
    <synopsis><![CDATA[ Returns the search service for the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchService cmdlet returns the SearchService object when the search service is updated or deleted For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchService [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchService = Get-SPEnterpriseSearchService
]]>
        </Code>
        <Remarks> This example obtains a reference to the search service of the current farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Returns the search service application for a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchServiceApplication cmdlet reads the SearchServiceApplication object when the search service application
 is updated or deleted For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchServiceApplication [[-Identity] <SearchServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection
>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA
]]>
        </Code>
        <Remarks> This example obtains a reference to a search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchServiceApplicationProxy </name>
    <synopsis><![CDATA[ Returns the search service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchServiceApplicationProxy cmdlet reads the SearchServiceApplicationProxy object when the search service a
pplication proxy is created, updated, or deleted. If the Identity parameter is not specified, this cmdlet returns the search service appl
ication proxy collection for the farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchServiceApplicationProxy [[-Identity] <SearchServiceApplicationProxyPipeBind>] [-AssignmentCollection <SPAssignment
Collection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssaProxy = Get-SPEnterpriseSearchServiceApplicationProxy -Identity SsaProxy
]]>
        </Code>
        <Remarks> This example obtains a reference to a search service application proxy with the name SsaProxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchServiceInstance </name>
    <synopsis><![CDATA[ Returns the search service instance for a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchServiceInstance cmdlet returns the SearchServiceInstance object when the object is created, updated, or
 deleted For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchServiceInstance [[-Identity] <SearchServiceInstancePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-L
ocal <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssInstance = Get-SPEnterpriseSearchServiceInstance -Local
]]>
        </Code>
        <Remarks> This example obtains a reference to the local search service instance </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPEnterpriseSearchSiteHitRule </name>
    <synopsis><![CDATA[ Returns the shared site hit rule. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchSiteHitRule cmdlet reads a SiteHitRule object when the site hit rule is created, updated, or deleted. A
 SiteHitRule object sets how many crawler sessions (threads) can simultaneously crawl the given site If the Identity parameter is not specified, this cmdlet returns the site hit rule collection for the specified search application
 For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPEnterpriseSearchSiteHitRule [[-Identity] <SiteHitRulePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-SearchService <
SearchServicePipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$shRule = Get-SPEnterpriseSearchSiteHitRule -Identity MySiteHitRule
]]>
        </Code>
        <Remarks> The following example obtains a reference to the site hit rule with the name MySiteHitRule </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPFarm </name>
    <synopsis><![CDATA[ Returns the local SharePoint farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPFarm cmdlet returns the local SharePoint farm. No parameters are used For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPFarm [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title>  </title>
        <Code>
          <![CDATA[
C:\PS>$f = Get-SPFarm
]]>
        </Code>
        <Remarks> This example stores the local farm in a variable </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPFarmConfig </name>
    <synopsis><![CDATA[ Returns a global property or a collection of global properties for the local farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPFarmConfig cmdlet retrieves global settings for the local farm that are not members of the SPFarm object. This cmdlet c
reates a new PSCustomObject object from the collection of properties returned from the local farm, and then adds this object to the pipel
ine. The PSCustomObject object can be read, or modified and passed to the Set-SPFarmConfig cmdlet to change parameter values The properties collected in the PSCustomObject object must be farm-wide settings, and must be configurable only once for the enti
re farm. The parameter name added to the PSCustomObject object must match exactly the input parameter name for the Set-the SPFarmConfig c
mdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPFarmConfig [-AssignmentCollection <SPAssignmentCollection>] [-ServiceConnectionPoint <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>$a = Get-SPFarmConfigPS> $a.AjaxTimeout = 200PS> $a | Set-SPFarmConfig
]]>
        </Code>
        <Remarks>
          This example uses the Get-SPFarmConfig cmdlet to add the Ajax Timeout setting to the PSCustomObject object, sets the value for Aj
          ax Timeout, and then passes PSCustomObject to the Set-SPFarmConfig cmdlet to change the Ajax Timeout setting. Ajax Timeout, a farm-wide s
          etting, is a member of the SPWebService object and cannot be accessed with a PowerShell cmdlet You can perform the same operations with either of the following commands
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPFeature </name>
    <synopsis><![CDATA[ Returns the SharePoint Features based on a given scope. ]]></synopsis>
    <description>
      <![CDATA[ The SPFeature cmdlet participates in a parameter set. All parameter sets take the Identity parameter, which can be either the rel
ative path of the SharePoint Feature (considered the feature name) or the GUID of a Feature definition. If the Identity parameter is prov
ided, the cmdlets attempt to find the given Feature definition or instance for the given scope. If no parameters are specified, all insta
lled features are returned The Get-SPFeature cmdlet behaves differently at each scope, returning the enabled Features at each level. If no scope is provided
, all installed Features are returned For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [<CommonPar
ameters>]
Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Farm <SwitchParameter>] [-L
imit <String>] [<CommonParameters>]
Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [-Sandboxed
 <SwitchParameter>] [-Site <SPSitePipeBind>] [<CommonParameters>]
Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [-Web <SPWe
bPipeBind>] [<CommonParameters>]
Get-SPFeature [[-Identity] <SPFeatureDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Limit <String>] [-WebApplic
ation <SPWebApplicationPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPFeature -Limit ALL | Where-Object {$_.Scope -eq "SITE"}
]]>
        </Code>
        <Remarks> This example returns a list of all installed SITE scoped Features </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite http://somesite | Get-SPWeb -Limit ALL |%{ Get-SPFeature -Web $_ } | Select DisplayName,ID -Unique
]]>
        </Code>
        <Remarks>
          This example returns the name and identifier (ID) of each uniquely enabled Feature on every SPWeb object in the site collection a
          t http://somesite
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPHelpCollection </name>
    <synopsis><![CDATA[ Returns Help collection files. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPHelpCollection cmdlet reads the specified Help collection files. If the Name parameter is not specified, this cmdlet re
turns all installed Help collection files For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPHelpCollection [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPHelpCollection
]]>
        </Code>
        <Remarks> This example gets all installed Help collection files </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPInfoPathFormsService </name>
    <synopsis><![CDATA[ Returns the InfoPath Forms Services in Microsoft SharePoint Server 2010 settings that are in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPInfoPathFormsService cmdlet reads the settings for the InfoPath Forms Services in SharePoint Server 2010 For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPInfoPathFormsService [-AssignmentCollection <SPAssignmentCollection>] [-Identity <SPFormsServicePipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPInfoPathFormsService
]]>
        </Code>
        <Remarks> This example displays the InfoPath Forms Services settings for the entire farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPInfoPathFormTemplate </name>
    <synopsis><![CDATA[ Returns a Microsoft InfoPath 2010 form template. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPInfoPathFormTemplate cmdlet reads a specific InfoPath 2010 form template or the collection of templates. If the Identit
y parameter is not specified, the cmdlet returns the collection of InfoPath 2010 form templates for the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPInfoPathFormTemplate [-Identity <SPFormTemplatePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE 1-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPInfoPathFormTemplate
]]>
        </Code>
        <Remarks>
          This example lists the Identity, DisplayName, and FormTemplateStatus property for each admininstrator-deployed InfoPath 2010 form
          template
        </Remarks>
      </example>
      <example>
        <title> ---------------EXAMPLE 2-------------- </title>
        <Code>
          <![CDATA[
C:\PS>"SomeFormTemplate.xsn" | Get-SPInfoPathFormTemplate | format-list
]]>
        </Code>
        <Remarks> This example lists all the properties of the specified InfoPath 2010 form template </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPInfoPathUserAgent </name>
    <synopsis><![CDATA[ Returns a user agent or all the currently defined user agents for the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPInfoPathUserAgent cmdlet reads the user agent specified in Identity. If the Identity parameter is not specified, this c
mdlet returns the collection of user agents for the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPInfoPathUserAgent [-Identity <SPUserAgentPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPInfoPathUserAgent
]]>
        </Code>
        <Remarks> This example displays a list of user agents in the entire farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPInfoPathWebServiceProxy </name>
    <synopsis><![CDATA[ Returns the Web proxy settings for the Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPInfoPathWebServiceProxy cmdlet reads the Web proxy settings for the SharePoint Web application specified in Identity For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPInfoPathWebServiceProxy -Identity <SPWebServiceProxyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>
]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPInfoPathWebServiceProxy -Identity "http://server_name"
]]>
        </Code>
        <Remarks> This example displays the Web service proxy settings for a specified Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPLogEvent </name>
    <synopsis><![CDATA[ Returns results from a Unified Logging Service (ULS) trace log. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPLogEvent cmdlet returns records from a ULS trace log file that match the criteria. If no parameters are specified, all 
records from all log files are returned. Use the StartTime and EndTime parameters to filter on a time range. The use of these parameters 
is recommended to optimize performance of this cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185 ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPLogEvent [-AssignmentCollection <SPAssignmentCollection>] [-AsString <SwitchParameter>] [-ContextKey <String[]>] [-Directory <Stri
ng>] [-EndTime <DateTime>] [-MinimumLevel <String>] [-StartTime <DateTime>] [<CommonParameters>]
Get-SPLogEvent [-AssignmentCollection <SPAssignmentCollection>] [-AsString <SwitchParameter>] [-ContextKey <String[]>] [-EndTime <DateTi
me>] [-File <String>] [-MinimumLevel <String>] [-StartTime <DateTime>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogEvent -MinimumLevel "Warning"
]]>
        </Code>
        <Remarks> This example returns all log entries equal to or more severe than Warning from the default log directory </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogEvent -Directory "C:\Logs" | Where-Object {$_.Level -eq "Warning"}
]]>
        </Code>
        <Remarks> This example returns all warning entries from log files in the C:\Logs directory </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogEvent -StartTime "12/04/2007 17:00" -EndTime "12/04/2007 18:00"
]]>
        </Code>
        <Remarks> This example returns error entries that occurred during a particular time range, which is culture-specific to the United States </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 4----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogEvent -ContextKey @("UserName" ,"SiteName")
]]>
        </Code>
        <Remarks> This example returns the contents of the most recent log file and adds the specified context key data </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 5----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogEvent | Where-Object {$_.Level -eq "Error" -and {$_.Area -eq "SharePoint Foundation "}
]]>
        </Code>
        <Remarks> This example returns all error entries related to SharePoint Foundation </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 6----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogEvent -ContextKey @("Name") | %{$_.ToString() + "'t" + $_.Context["Name"]}
]]>
        </Code>
        <Remarks> This example returns the contents of the log file and adds context data </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPLogLevel </name>
    <synopsis><![CDATA[ Returns a list of objects or diagnostic levels. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPLogLevel cmdlet displays a list of objects or diagnostic levels based on the criteria specified. If no parameter is spe
cified, a list of all diagnostic levels for all categories is returned For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPLogLevel [-AssignmentCollection <SPAssignmentCollection>] [-Identity <String[]>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogLevel
]]>
        </Code>
        <Remarks> This example displays throttle levels for all categories </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogLevel -Identity "Category1"
]]>
        </Code>
        <Remarks> This example displays the throttle level for the Category1 category </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>"Cat1", "Cat2", "Cat3" | Get-SpLogLevel
]]>
        </Code>
        <Remarks> This example displays the throttle level for multiple categories </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 4----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPLogLevel -Identity "Area:*"
]]>
        </Code>
        <Remarks> This example displays the throttle level for all categories in one area </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPManagedAccount </name>
    <synopsis><![CDATA[ Retrieves accounts registered in the configuration database. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPManagedAccount cmdlet participates in a parameter set. It returns the managed accounts that match the given scope. The 
scope can be any one of the following values: Web application, service, or server For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPManagedAccount [[-Identity] <SPManagedAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Service <SPServicePipeB
ind>] [<CommonParameters>]
Get-SPManagedAccount [[-Identity] <SPManagedAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-WebApplication <SPWebAp
plicationPipeBind>] [<CommonParameters>]
Get-SPManagedAccount [[-Identity] <SPManagedAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Server <SPServerPipeBin
d>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPManagedAccount
]]>
        </Code>
        <Remarks> This example displays all the managed accounts in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPManagedPath </name>
    <synopsis><![CDATA[ Returns all managed paths that match the given criteria. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPManagedPath cmdlet returns the SharePoint managed path that matches the provided Identity for either a Web Application,
 site collection or for all HostHeader site collections.  If an Identity parameter is not provided, all managed paths for the given scope
 are returned HostHeader sites (no matter the Web application in which they are contained) share a single set of managed paths.  Use the HostHe
ader parameter to return host header managed paths For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185 ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPManagedPath [[-Identity] <SPPrefixPipeBind>] -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollec
tion>] [<CommonParameters>]
Get-SPManagedPath [[-Identity] <SPPrefixPipeBind>] -HostHeader <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPManagedPath -WebApplication http://sitename
]]>
        </Code>
        <Remarks> This example returns all managed paths for the specified Web application </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPManagedPath -identity "Sites" -HostHeader
]]>
        </Code>
        <Remarks> This example gets the Sites managed path from the HostHeader managed paths </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPMetadataServiceApplication </name>
    <synopsis><![CDATA[ Returns the properties of a service application or a collection of service applications. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPMetadataServiceApplication cmdlet to read the properties of a specified service application or the collection of se
rvice applications for the Metadata Service. If the Identity parameter is not specified, the cmdlet returns the collection of service app
lications in the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPMetadataServiceApplication -Identity <SPMetadataServiceCmdletPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonPa
rameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPMetadataServiceApplication -Identity "MetadataServiceApp1"
]]>
        </Code>
        <Remarks> This example retrieves an existing Metadata Service application} } </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPMetadataServiceApplicationProxy </name>
    <synopsis><![CDATA[ Returns the properties of a service application proxy or a collection of service application proxies. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPMetadataServiceApplicationProxy cmdlet to read the properties of a specified service application proxy, or the coll
ection of service application proxies, for the Metadata Service. If the Identity parameter is not specified, the cmdlet returns the colle
ction of service application proxies in the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPMetadataServiceApplicationProxy -Identity <SPMetadataServiceProxyCmdletPipeBind> [-AssignmentCollection <SPAssignmentCollection>] 
[<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1"
]]>
        </Code>
        <Remarks> This example retrieves an existing Metadata Service application proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPMobileMessagingAccount </name>
    <synopsis><![CDATA[ Retrieves mobile messaging accounts for the specified Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPMobileMessagingAccount cmdlet retrieves the specified mobile messaging accounts for the specified Web application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185 ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPMobileMessagingAccount [[-Identity] <SPMobileMessagingAccountPipeBind>] -WebApplication <SPWebApplicationPipeBind> [-AssignmentCol
lection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPMobileMessagingAccount -WebApplication http://sitename
]]>
        </Code>
        <Remarks> This example retrieves the current mobile account settings information of the Web application http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPPerformancePointSecureDataValues </name>
    <synopsis><![CDATA[ Displays unattended service account settings. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPPerformancePointSecureDataValues cmdlet displays global settings for the unattended service account For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPPerformancePointSecureDataValues [-ServiceApplication] <SPPerformancePointMonitoringServiceApplicationPipeBind> [-AssignmentCollec
tion <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPPerformancePointServiceApplication | Get-SPPerformancePointSecureDataValues
]]>
        </Code>
        <Remarks> This example shows how to get the unattended service account settings using a service application pipe bind </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPPerformancePointSecureDataValues -ServiceApplication "PerformancePoint Service Application"
]]>
        </Code>
        <Remarks> This example shows how to specify the service application by using the service application name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPPerformancePointServiceApplication </name>
    <synopsis><![CDATA[ Returns a PerformancePoint Service application object and properties. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPPerformancePointServiceApplication cmdlet to read a PerformancePoint Service application object and properties. If 
the Identity parameter is not specified, the cmdlet returns the collection of PerformancePoint Service applications in the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPPerformancePointServiceApplication [[-Identity] <SPPerformancePointMonitoringServiceApplicationPipeBind>] [-AssignmentCollection <
SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title>  </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPPerformancePointServiceApplication "PPSApp_01"
]]>
        </Code>
        <Remarks> This example creates a PerformancePoint Service application named PPSApp_01 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPPerformancePointServiceApplicationTrustedLocation </name>
    <synopsis><![CDATA[ Returns a trusted location object and properties for a PerformancePoint Service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPPerformancePointMonitoringServiceApplicationTrustedLocation cmdlet to read a trusted location object and properties
. If the Identity parameter is not specified, this cmdlet returns the list of all trusted locations and their properties for a Performanc
ePoint Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPPerformancePointServiceApplicationTrustedLocation [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] 
[-Identity <SPPerformancePointMonitoringServiceApplicationTrustedLocationPipeBind>] [-ServiceApplication <SPPerformancePointMonitoringSe
rviceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPPerformancePointServiceApplication PPSApp_01 | Get-SPPerformancePointServiceApplicationTrustedLocation -Identity $_.ID | sel
ect *
]]>
        </Code>
        <Remarks> This example retrieves TrustedLocation information for the PPSApp_01 PerformancePoint Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPPluggableSecurityTrimmer </name>
    <synopsis>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Get-SPPluggableSecurityTrimmer [-UserProfileApplicationProxyId] <Guid> [-AssignmentCollection <SPAssignmentCollection>] [-Verbose] [-Deb
ug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>] [-OutVar
iable <String>] [-OutBuffer <Int32>]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPProcessAccount </name>
    <synopsis><![CDATA[ Returns a system account or a managed account. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPProcessAccount cmdlet returns a system account or a managed account and creates the SPProcessAccountPipeBind object. Al
l operations that can accept an account can accept the SPProcessAccountPipeBind in place of the SPManagedAccountPipeBind For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPProcessAccount [-AssignmentCollection <SPAssignmentCollection>] [-NetworkService <SwitchParameter>] [<CommonParameters>]
Get-SPProcessAccount [-AssignmentCollection <SPAssignmentCollection>] [-LocalSystem <SwitchParameter>] [<CommonParameters>]
Get-SPProcessAccount [-AssignmentCollection <SPAssignmentCollection>] [-LocalService <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPProcessAccount -NetworkService
]]>
        </Code>
        <Remarks> This example creates the SPProcessAccountPipeBind type by using the NetworkService account </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPProcessAccount -NetworkService | New-SPIisWebServiceApplicationPool -Account $_
]]>
        </Code>
        <Remarks>
          This example creates an SPIisWebServiceApplicationPool account by using the NetworkService account returned by the Get-SPProcessA
          ccount cmdlet
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPProduct </name>
    <synopsis><![CDATA[ Returns a list of the SharePoint-related products installed in the farm and the versions of all updates installed for each product. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPProduct cmdlet returns a list of the SharePoint-related products installed in the farm and the versions of all updates 
installed for each product. By default this cmdlet returns the list of SharePoint-related products installed in the farm. Use the Local p
arameter to get only information about the local server or for a specific server to get the list, use the Server parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPProduct [-AssignmentCollection <SPAssignmentCollection>] [-Local <SwitchParameter>] [<CommonParameters>]
Get-SPProduct [-AssignmentCollection <SPAssignmentCollection>] [-Server <SPServerPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPProduct -Local
]]>
        </Code>
        <Remarks> This example displays the SharePoint-related products installed on the local server </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPProfileServiceApplicationSecurity </name>
    <synopsis><![CDATA[ Returns permission and identity information. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPProfileServiceApplicationSecurity cmdlet to display permission and identity information for the following User Prof
ile objects:} } - Read individual My Sites} } - Use Personal Features} } - Use Social Features} } - Create Personal Site} } For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPProfileServiceApplicationSecurity -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAs
signmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-Type <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$UPAProxy = Get-SPServiceApplicationProxy -Identity "UPA proxy 1"

C:\PS>Get- SPProfileServiceApplicationSecurity - ProfileServiceApplicationProxy $UPAProxy -Type MySiteReaderACL
]]>
        </Code>
        <Remarks> This example displays MySite information on UPA Proxy 1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSearchService </name>
    <synopsis><![CDATA[ Returns a search service. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSearchService cmdlet reads the SPSearch object when the cmdlet updates a search service For permissions and the most current information about Windows PowerShell for SharePoint Foundation 2010, see TechNet (http://go.
microsoft.com/fwlink/?LinkId=163184) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSearchService [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$searchService = Get-SPSearchService
]]>
        </Code>
        <Remarks> This example obtains a reference to the search service object </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSearchServiceInstance </name>
    <synopsis>
      <![CDATA[ Get-SPSearchServiceInstance [[-Identity] <SPSearchServiceInstancePipeBind>] [-Local] [-AssignmentCollection <SPAssignmentCollection>] [-
Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <Stri
ng>] [-OutVariable <String>] [-OutBuffer <Int32>]
 ]]>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Get-SPSearchServiceInstance [[-Identity] <SPSearchServiceInstancePipeBind>] [-Local] [-AssignmentCollection <SPAssignmentCollection>] [-
Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <Str
ing>] [-OutVariable <String>] [-OutBuffer <Int32>]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSecureStoreApplication </name>
    <synopsis><![CDATA[ Returns a Secure Store application. ]]></synopsis>
    <description><![CDATA[ The Get-SPSecureStoreApplication cmdlet returns a Secure Store application ]]></description>
    <syntax>
      <![CDATA[
Get-SPSecureStoreApplication -Name <String> -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentCollection>] 
[<CommonParameters>]
Get-SPSecureStoreApplication -All <SwitchParameter> -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentColle
ction>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApplication"
]]>
        </Code>
        <Remarks> This example gets the Secure Store application for the target application with the name ContosoTargetApplication </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>-SPSecureStoreApplication -ServiceContext http://contoso -All
]]>
        </Code>
        <Remarks> This example returns all of the Secure Store applicationshttp://consoso </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSecurityTokenServiceConfig </name>
    <synopsis><![CDATA[ Returns the security token service (STS) for the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSecurityTokenServiceConfig cmdlet reads the security token service (STS) for the farm. An STS authenticates security to
kens in incoming SOAP messages For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSecurityTokenServiceConfig [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get - SPSecurityTokenServiceConfig | Set -SPSecurityTokenServiceConfig -ServiceTokenLifetime 1000
]]>
        </Code>
        <Remarks>
          This example gets the security token service (STS) for the farm and sets the expiration for the service token cache to 1000 minut
          es
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServer </name>
    <synopsis><![CDATA[ Returns the server or servers in the farm that match the given identity. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServer cmdlet returns the SPServer object for the given identity (if it exists in the farm). If no parameters are speci
fied, the cmdlet returns all servers in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185 ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServer [[-Identity] <SPServerPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServer
]]>
        </Code>
        <Remarks> This example returns all servers in the local farm in a list </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServer | Where{ $_.NeedsUpgrade -eq $TRUE}
]]>
        </Code>
        <Remarks> This example returns a list of all servers in the farm that need an upgrade </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceApplication </name>
    <synopsis><![CDATA[ Returns the specified service application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceApplication cmdlet returns the service application specified by the Identity parameter. If no parameter is speci
fied, the cmdlet returns all service applications in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceApplication [[-Identity] <SPServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Name <String>] 
[<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplication
]]>
        </Code>
        <Remarks> This example returns all service applications in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceApplicationEndpoint </name>
    <synopsis><![CDATA[ Returns the endpoint of a service application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceApplicationEndpoint cmdlet sets the host of a service endpoint. Use the second parameter set and do not specify 
the Name parameter to return a collection of all endpoints for the specified service application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceApplicationEndpoint [-Identity] <SPServiceEndpointPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParame
ters>]
Get-SPServiceApplicationEndpoint -ServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-N
ame <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get- SPServiceApplicationEndpoint -ServiceApplication "ServiceSubApp1"
]]>
        </Code>
        <Remarks> This example returns the SPServiceEndpoint object based on the specified service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceApplicationPool </name>
    <synopsis><![CDATA[ Returns the specified Internet Information Services (IIS) application pool. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceApplicationPool cmdlet returns the IIS application pool specified by the Identity parameter, or returns all appl
ication pools if the Identity parameter is not specified For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185 ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceApplicationPool [[-Identity] <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<C
ommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplicationPool
]]>
        </Code>
        <Remarks> This example returns all the service application pools in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceApplicationProxy </name>
    <synopsis><![CDATA[ Returns an instance of the specified service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceApplicationProxy cmdlet returns an instance of the service application proxy specified by the Identity parameter
 For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceApplicationProxy [[-Identity] <SPServiceApplicationProxyPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<Commo
nParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplicationProxy
]]>
        </Code>
        <Remarks> This example retrieves all the service application proxies in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceApplicationProxyGroup </name>
    <synopsis><![CDATA[ Returns the proxy group for the specified service application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceApplicationProxyGroup cmdlet displays a list of the proxy groups in the farm. To display a specific proxy group,
 use the Identity parameter. If no parameter value is specified, a list of all proxy groups is displayed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceApplicationProxyGroup [[-Identity] <SPServiceApplicationProxyGroupPipeBind>] [-AssignmentCollection <SPAssignmentCollection
>] [<CommonParameters>]
Get-SPServiceApplicationProxyGroup -Default <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplicationProxyGroup
]]>
        </Code>
        <Remarks> This example retrieves all of the service application proxy groups in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceApplicationSecurity </name>
    <synopsis><![CDATA[ Returns the SPObjectSecurity object for a service application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceApplicationSecurity cmdlet returns a security object for the specified service application. Use this cmdlet with
 the Grant-SPObjectSecurity and Set-SPServiceApplicationSecurity cmdlets to manage security for a service application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceApplicationSecurity [-Identity] <SPServiceApplicationPipeBind> [-Admin <SwitchParameter>] [-AssignmentCollection <SPAssignm
entCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$security = Get-SPServiceApplicationSecurity $serviceApp -Admin
Grant-SPObjectSecurity $security $principal "Full Control"
Set-SPServiceApplicationSecurity $serviceApp -Admin $security
]]>
        </Code>
        <Remarks>
          This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on a service application, and adds a ne
          w user principal to that ACL. The new user is an administrator for the service application $serviceApp
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceContext </name>
    <synopsis><![CDATA[ Returns a service context. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceContext cmdlet returns a service context or a collection of service contexts. Specify the Site parameter to retu
rn an individual service context, or specify the SiteSubscription parameter to return a collection of service contexts For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceContext [-Site] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
Get-SPServiceContext -SiteSubscription <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>
]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>$sitesub = Get-SPSiteSubscription http://my.contoso.com/

C:\PS>Get-SPServiceContext $sitesub
]]>
        </Code>
        <Remarks> This example returns the service context for a site in a hosted environment </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceHostConfig </name>
    <synopsis><![CDATA[ Returns the common Web service settings. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceHostConfig returns the common Web service settings For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceHostConfig [-AssignmentCollection <SPAssignmentCollection>] [-Default <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get- SPServiceHostConfig
]]>
        </Code>
        <Remarks> This example displays the Web service settings </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPServiceInstance </name>
    <synopsis><![CDATA[ Returns the services instance for a specific server or the entire farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPServiceInstance cmdlet returns the services instance specified by the Identity parameter for a specific server. If the 
Server parameter is not specified, the Get-SPServiceInstance cmdlet returns results for the entire farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPServiceInstance [[-Identity] <SPServiceInstancePipeBind>] [-All <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>
] [<CommonParameters>]
Get-SPServiceInstance -Server <SPServerPipeBind> [-All <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParam
eters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceInstance -Server ServerA
]]>
        </Code>
        <Remarks> This example displays the service instances from a given server </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSessionStateService </name>
    <synopsis><![CDATA[ Returns the properties of the session state service, including time-out and database settings. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSessionStateService cmdlet reads the properties of the session state service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSessionStateService [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSessionStateService
]]>
        </Code>
        <Remarks> This example returns the current configuration of the session state service </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPShellAdmin </name>
    <synopsis><![CDATA[ Returns the names of all users who have the SharePoint_Shell_Access role. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPShellAdmin cmdlet to return the names of all users who have the SharePoint_Shell_Access role in a database For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPShellAdmin [[-database] <SPDatabasePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPShellAdmin -database WSS_Content
]]>
        </Code>
        <Remarks> This example returns the name of each user who has the SharePoint_Shell_Access role in the WSS_Content database </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSite </name>
    <synopsis><![CDATA[ Returns all site collections that match the given criteria. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSite cmdlet returns either a single site that matches the Identity parameter, or all the sites that match the Filter pa
rameter for the specified scope. The scopes are the WebApplication, ContentDatabase , and SiteSubscription parameters. If none of these s
copes is provided, the scope is the farm. If the scope is specified with no Filter parameter, all sites in that scope are returned The Identity parameter supports providing a partial URL that ends in a wildcard character (*). All site collections that match th
is partial URL for the specified scope are returned. Additionally, if the Regex parameter is provided, the Identity parameter is treated 
as a regular expression and any site collection with a URL provided in the given scope that matches the expression is returned The Filter parameter is a server-side filter for certain site collection properties that are stored in the content database; with
out the Filter parameter, filtering on these properties is a slow process. These site collection properties are Owner, SecondaryOwner, an
d LockState. The Filter parameter is a script block that uses the same syntax as a Where-Object statement, but is run server-side for fas
ter results Valid values for LockState are, Unlock, NoAdditions, ReadOnly, NoAccess It is important to note that every site collection returned by the Get-SPSite cmdlet is automatically disposed of at the end of t
he pipeline. To store the results of Get-SPSite in a local variable, the Start-SPAssignment and Stop-SPAssignment cmdlets must be used to
 avoid memory leaks For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSite [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Filter <ScriptBlock>] [-Limit <String>] [-W
ebApplication <SPWebApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Get-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Filter <Script
Block>] [-Limit <String>] [-Regex <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Get-SPSite -ContentDatabase <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] 
[-Filter <ScriptBlock>] [-Limit <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Get-SPSite -SiteSubscription <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]
] [-Filter <ScriptBlock>] [-Limit <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite 'http://sitename' | Get-SPWeb -Limit All | Select Title
]]>
        </Code>
        <Remarks> This example gets the collection of subweb titles in site collection at http://sitename </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite -ContentDatabase "b399a366-d899-4cff-8a9b-8c0594ee755f" | Format-Table -Property Url, Owner, SecondaryOwner
]]>
        </Code>
        <Remarks> This example gets a subset of data from all of the sites in the content database b399a366-d899-4cff-8a9b-8c0594ee755f </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPAssignment -Global

C:\PS>$s = Get-SPSite -Identity http://MyApp/Sites/Site1

C:\PS>$s.Url

C:\PS>Stop-SPAssignment -Global
]]>
        </Code>
        <Remarks>
          This example gets the sites specified by the Identity parameter and inserts the results in the variable s} } The previous example uses the Global method of assignment collection. The Global method is easier to use but the contents of this
          object grows quickly. Be careful not to run a Get-SPSite command that returns many results while global assignment is enabled
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 4--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$GC = Start-SPAssignment

C:\PS>$Sites = $GC | Get-SPSite -Filter {$_.Owner -eq "DOMAIN\JDoe"} -Limit 50

C:\PS>Stop-SPAssignment $GC
]]>
        </Code>
        <Remarks>
          This example gets the first 50 sites owned by user DOMAIN\JDoe by using a server-side query, and assigns them to a local variable
           This example uses advanced assignment collection methods
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 5--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://sitename | Get-SPSite -Limit All |ForEach-Object {$sum=0}{ $sum+=$_.Usage.Storage }{$sum}
]]>
        </Code>
        <Remarks> This example shows a command that returns the sum of the disk space usage for all sites in a given Web application </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 6--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite -identity "http://localserver/(my|personal)/sites" -Regex
]]>
        </Code>
        <Remarks> This example returns all sites that match the given regular expression The Quotes on the Identity parameter are required when the Regex parameter is used </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 7--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite http://sitename/sites/teams/* -Limit 100
]]>
        </Code>
        <Remarks> This example gets up to 100 of the sites under the URL http://sitename/sites/teams </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 8--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite | select url, @{Expression={$_.Usage.Storage}}
]]>
        </Code>
        <Remarks> This example gets the amount of storage used by a site collection, by using the storage field of the .UsageInfo property </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSiteAdministration </name>
    <synopsis>
      <![CDATA[ Returns a site administration object that allows farm administrators to view certain information about site collections to which they mi
ght not have access. ]]>
    </synopsis>
    <description>
      <![CDATA[ The Get-SPSiteAdminitration cmdlet returns a site administration object that allows farm administrators to view certain informati
on about site collections to which they might not have access For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSiteAdministration [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Filter <ScriptBlock>] [-Limit
 <String>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Get-SPSiteAdministration [-Identity] <SPSiteAdministrationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchP
arameter>]] [-Filter <ScriptBlock>] [-Limit <String>] [-Regex <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Get-SPSiteAdministration -ContentDatabase <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switc
hParameter>]] [-Filter <ScriptBlock>] [-Limit <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Get-SPSiteAdministration -SiteSubscription <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-Filter <ScriptBlock>] [-Limit <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteAdministration | Select -Property Url, OwnerLoginName, @{Name="Storage";Expression={$_.Quota.StorageMaximumLevel}}
]]>
        </Code>
        <Remarks>
          This example gets a subset of data from all of the sites in the content database with the URL b399a366-d899-4cff-8a9b-8c0594ee755
          f (farm administrator does not require access). This command uses the calculated property Storage to display the maximum storage value fo
          r the content database
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPAssignment -Global
$s = Get-SPSiteAdministration -Identity http://MyApp/Sites/Site1
$s.Url
Stop-SPAssignment -Global
]]>
        </Code>
        <Remarks>
          This example gets the site collections specified by the Identity parameter and inserts the results into the variable s. This exam
          ple uses the Global method of garbage collection. This method is easier to use but grows quickly. Do not run a Get-SPSite command that re
          turns many results while global assignment is on
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$GC = Start-SPAssignment
$Sites = $GC | Get-SPSiteAdministration -Filter {$_.Owner -eq "DOMAIN\JDoe"} -Limit 50
Stop-SPAssignment $GC
]]>
        </Code>
        <Remarks>
          This example gets the first 50 sites owned by user DOMAIN\JDoe by using a server-side query, and assigns the returned sites to a
          local variable. This command uses advanced assignment collection methods
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 4------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://sitename | Get-SPSiteAdministration -Limit All |ForEach-Object {$sum=0}{ $sum+=$_.DiskUsed }{$sum}
]]>
        </Code>
        <Remarks> This command returns the sum of the disk space usage for all sites in the specified Web application </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 5------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://sitename | Get-SPSiteAdministration -Limit ALL | Select URL
]]>
        </Code>
        <Remarks> This example gets the URLs for all site collections in a Web application </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 6------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteAdministration -identity "http://localserver/(my|personal)/sites" -Regex
]]>
        </Code>
        <Remarks>
          This example returns all sites that match the given regular expression. The quotation marks around the value specified for the Id
          entity parameter are required when using the Regex flag
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 7------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite "http://sitename/sites/teams/*" -Limit 100
]]>
        </Code>
        <Remarks> This example gets up to 100 of the sites under the URL http://sitename/sites/teams </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSiteSubscription </name>
    <synopsis><![CDATA[ Returns the site subscription for the given URL or all site subscriptions in the local farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSiteSubscription cmdlet returns the site subscription for the given URL when the Identity parameter is used. If no para
meter is specified, all unique site subscriptions in the farm are listed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSiteSubscription [[-Identity] <SPSiteSubscriptionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$SiteSub = Get-SPSiteSubscription http://Contoso.com

C:\PS>$SiteSub = Get-SPSite http://contoso.com | Get-SPSiteSubscription
]]>
        </Code>
        <Remarks> This example retrieves the site subscription for http://Contoso.com </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSiteSubscriptionConfig </name>
    <synopsis><![CDATA[ Returns the configuration properties of a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSiteSubscriptionConfig cmdlet returns the configuration properties of a site subscription For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSiteSubscriptionConfig [-Identity] <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameter
s>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscriptionConfig http://contoso.com | Select FeatureSet
]]>
        </Code>
        <Remarks> This example gets the feature set ID for the site subscription that contains the Web site http://contoso.com </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSiteSubscriptionEdiscoveryHub </name>
    <synopsis><![CDATA[ Displays the eDiscovery hub for a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPSiteSubscriptionEdiscoveryHub cmdlet to display the site collection configured as the eDiscovery hub for the specif
ied site subscription For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSiteSubscriptionEdiscoveryHub -Identity <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<
SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscriptionEdiscoveryHub -Identity http://contoso.com
]]>
        </Code>
        <Remarks> This example displays the eDiscovery hub for the specified site collection </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSiteSubscriptionEdiscoverySearchScope </name>
    <synopsis><![CDATA[ Displays the search scope for the eDiscovery hub of the specified site collection. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPSiteSubscriptionEdiscoverySearchScope cmdlet to retrieve the search scope that has been configured for the eDiscove
ry hub of the specified site subscription For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSiteSubscriptionEdiscoverySearchScope -Identity <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Co
nfirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscriptionEdiscoverySearchScope - Identity http://contoso.com
]]>
        </Code>
        <Remarks> This example displays the search scope for the eDiscovery hub for the specified site collection </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSiteSubscriptionFeaturePack </name>
    <synopsis><![CDATA[ Retrieves available SharePoint Feature sets or the Feature set assigned to a given site subscription. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSiteSubscriptionFeaturePack cmdlet retrieves available SharePoint Feature sets or the Feature set assigned to a given s
ite subscription Be careful when you assign Feature sets to variables because changes to the Feature set are not reflected until the variable is r
efreshed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSiteSubscriptionFeaturePack [[-Identity] <SPSiteSubscriptionFeaturePackPipeBind>] [-AssignmentCollection <SPAssignmentCollection>]
 [<CommonParameters>]
Get-SPSiteSubscriptionFeaturePack [-AssignmentCollection <SPAssignmentCollection>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [<Co
mmonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get- SPSiteSubscriptionFeaturePack
]]>
        </Code>
        <Remarks> This example returns all defined Feature sets in the local farm </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscriptionFeaturePack -SiteSubscription http://contoso.com | ForEach{ $_.FeatureDefinitions }
]]>
        </Code>
        <Remarks>
          This example returns the list (name, ID, and scope) of all Features allowed in the Feature set that is currently assigned to the
          site subscription of http://contoso.com
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSiteSubscriptionMetadataConfig </name>
    <synopsis><![CDATA[ Returns the site subscription configuration settings for a Metadata Service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPSiteSubscriptionMetadataConfig cmdlet to read the site subscription configuration settings for a specified shared s
ervice application for the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSiteSubscriptionMetadataConfig -Identity <SPSiteSubscriptionPipeBind> -ServiceProxy <SPMetadataServiceProxyCmdletPipeBind> [-Assig
nmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscriptionMetadataConfig -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2"
]]>
        </Code>
        <Remarks> This example retrieves the site subscription-specific settings for an existing partitioned Metadata Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPSolution </name>
    <synopsis><![CDATA[ Returns a specified SharePoint solution. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPSolution cmdlet returns a specified SharePoint solution. If the Identity parameter is not specified, this cmdlet return
s the collection of all installed SharePoint solutions in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPSolution [[-Identity] <SPSolutionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSolution
]]>
        </Code>
        <Remarks> This example returns the collection of all installed SharePoint solutions in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPStateServiceApplication </name>
    <synopsis><![CDATA[ Returns state service applications on the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPStateServiceApplication cmdlet returns a state service application on the farm. If the Identity parameter is not specif
ied, this cmdlet returns the collection of all state service applications on the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPStateServiceApplication [[-Identity] <SPStateServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confi
rm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceApplication
]]>
        </Code>
        <Remarks> This example displays all state service applications in the farm </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceApplication -Identity "StateServiceApp1"
]]>
        </Code>
        <Remarks> This example displays a specific state service application in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPStateServiceApplicationProxy </name>
    <synopsis><![CDATA[ Returns state service application proxies on the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPStateServiceApplicationProxy cmdlet returns a state service application proxy on the farm. If the Identity parameter is
 not specified, this cmdlet returns the collection of all state service application proxies on the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPStateServiceApplicationProxy [[-Identity] <SPStateServiceApplicationProxyPipeBind>] [-AssignmentCollection <SPAssignmentCollection
>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceApplicationProxy
]]>
        </Code>
        <Remarks> This example displays all the state service application proxies on the farm </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceApplicationProxy -Identity 81dc50e0-c0f9-4d2c-8284-bb03bb1ea676
]]>
        </Code>
        <Remarks> This example displays a specific state service application proxy on the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Returns a state service database. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPStateServiceDatabase cmdlet returns a state service database on the farm. If the Identity parameter is not specified, t
his cmdlet returns the collection of all state service databases on the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPStateServiceDatabase [[-Identity] <SPStateDatabasePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Get-SPStateServiceDatabase [[-ServiceApplication] <SPStateServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] 
[-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1---------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceDatabase
]]>
        </Code>
        <Remarks> This example displays all of the state service databases on the farm </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b
]]>
        </Code>
        <Remarks> This example displays a specific state service database in the farm </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 3-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceDatabase -ServiceApplication "StateServiceApp1"
]]>
        </Code>
        <Remarks> This example displays all state service databases associated with a specific service </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPTaxonomySession </name>
    <synopsis><![CDATA[ Returns a TaxonomySession object. ]]></synopsis>
    <description>
      <![CDATA[ Use the Get-SPTaxonomySession cmdlet to get a TaxonomySession object. A TaxonomySession object contains the set of metadata term 
stores for a taxonomy session For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPTaxonomySession -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$session = Get-SPTaxonomySession -Site "http://sitename"
]]>
        </Code>
        <Remarks>
          This example retrieves a TaxonomySession object, which can be used to access term stores associated with the Web application for
          a site
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPTimerJob </name>
    <synopsis><![CDATA[ Returns timer jobs. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPTimerJob cmdlet reads a specified timer job, timer jobs of a specified type, or timer jobs defined for a specified scop
e. If no parameters are specified, this cmdlet returns all timer job definitions for the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPTimerJob [[-Identity] <SPTimerJobPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Type <String>] [-WebApplication <SP
WebApplicationPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTimerJob -WebApplication "http://servername" | select Name, DisplayName
]]>
        </Code>
        <Remarks> This example displays all timer jobs for a specified Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPTopologyServiceApplication </name>
    <synopsis><![CDATA[ Displays properties of the topology service application for the current farm. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPTopologyServiceApplication cmdlet displays the advanced properties of an application when the Identity parameter is use
d For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPTopologyServiceApplication [[-Identity] <SPTopologyWebServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>
] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTopologyServiceApplication
]]>
        </Code>
        <Remarks> This example displays properties of the topology service application for the current farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPTopologyServiceApplicationProxy </name>
    <synopsis><![CDATA[ Retrieves the topology service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPTopologyServiceApplicationProxy cmdlet retrieves the local topology service application proxy For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPTopologyServiceApplicationProxy [[-Identity] <SPTopologyWebServiceProxyPipeBind>] [-AssignmentCollection <SPAssignmentCollection>]
 [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTopologyServiceApplicationProxy
]]>
        </Code>
        <Remarks> This example displays the topology service application proxy in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPTrustedIdentityTokenIssuer </name>
    <synopsis><![CDATA[ Returns an identity provider. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPTrustedIdentityTokenIssuer cmdlet returns an identity provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPTrustedIdentityTokenIssuer [[-Identity] <SPTrustedIdentityTokenIssuerPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [
<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------------EXAMPLE 1------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$trustedsts = get - SPTrustedIdentityTokenIssuer "LiveIDSTS"
]]>
        </Code>
        <Remarks> This example gets a trusted identity token issuer </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPTrustedRootAuthority </name>
    <synopsis><![CDATA[ Returns a trusted root authority. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPTrustedRootAuthority cmdlet returns a trusted root authority. If a certificate file is used, it must have only one X509
 certificate without private keys, otherwise an exception is raised For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPTrustedRootAuthority [[-Identity] <SPTrustedRootAuthorityPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParam
eters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$rootauthority = Get - SPTrustedRootAuthority -Name "WFEFarm1"
]]>
        </Code>
        <Remarks> This example creates a new trusted root authority, WFEFarm1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPTrustedServiceTokenIssuer </name>
    <synopsis><![CDATA[ Returns the object that represents the farm trust. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPTrustedServiceTokenIssuer cmdlet returns the object that represents the farm trust For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPTrustedServiceTokenIssuer [[-Identity] <SPTrustedServiceTokenIssuerPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<C
ommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get - SPTrustedServiceTokenIssuer "WFEFarm1"
]]>
        </Code>
        <Remarks> This example gets the trusted services token issuer WFEFarm1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPUsageApplication </name>
    <synopsis><![CDATA[ Returns a specified usage application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPUsageApplication cmdlet return a specified usage application. If the Identity parameter is not specified, the cmdlet re
turns the local usage application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPUsageApplication [[-Identity] <SPUsageApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-UsageService <SPUsa
geServicePipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPUsageApplication -Identity "Usage and Health data collection"
]]>
        </Code>
        <Remarks> This example returns the usage application named, Usage and Health data collection} } </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPUsageDefinition </name>
    <synopsis><![CDATA[ Returns a usage definition object. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPUsageDefinition cmdlet reads a usage definition object. If the Identity parameter is not specified, this cmdlet returns
 the collection of usage definitions in the farm. A usage definition object defines a specific type of usage For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPUsageDefinition [[-Identity] <SPUsageDefinitionPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPUsageDefinition -Identity "Page Requests"
]]>
        </Code>
        <Remarks> This example returns the SPRequestUsage provider on the local farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPUsageService </name>
    <synopsis><![CDATA[ Returns a usage service. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPUsageService cmdlet returns the specified usage service. If the Identity parameter is not specified, the cmdlet returns
 the local usage service For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPUsageService [[-Identity] <SPUsageServicePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPUsageService -Identity 57055d99-9914-4af6-a3bf-7b76e3f231c2
]]>
        </Code>
        <Remarks> This example returns a SPUsageService object of the specified ID </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPUser </name>
    <synopsis><![CDATA[ Returns the user account or accounts that match a given search criteria. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPUser cmdlet returns all SharePoint user accounts that match the scope given by the Identity, Web, or Group parameters The Identity parameter can use the alias of a user for returning exact matches. However, a scope must be provided if the Get-SPUs
er cmdlet is to work For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPUser [[-Identity] <SPUserPipeBind>] -Web <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Group <SPGroupPipeBind
>] [-Limit <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPUser -Web "http://zsharepoint2" -Group "Viewers"
]]>
        </Code>
        <Remarks> This example returns all members of the group Viewers on the Web site http://zsharepoint2 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPUserSolution </name>
    <synopsis><![CDATA[ Returns a specified sandboxed solution. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPUserSolution cmdlet returns a specified sandboxed solution. If the Identity parameter is not specified, this cmdlet ret
urns the collection of sandboxed solutions in the SharePoint farm. A user solution is a sandboxed solution For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPUserSolution [[-Identity] <SPUserSolutionPipeBind>] -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPUserSolution -Site http://sitename
]]>
        </Code>
        <Remarks> This example displays information about sandboxed solutions in the site http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWeb </name>
    <synopsis><![CDATA[ Returns all subsites that match the given criteria. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPWeb cmdlet returns all subsites that match the scope given by the Identity parameter. All subsites that meet the criter
ia are returned The Identity can be either the full URL or a relative path. If you specify a relative path, you must also specify the Site parame
ter to identify the site collection from which to return the subsite The Identity parameter also supports providing a partial URL that ends in a wildcard character (*). All subsites that match this 
partial URL for the specified scope are returned. Additionally, if the Regex parameter is provided, the Identity parameter is treated as 
a regular expression and any subweb with a URL provided in the given scope that matches the expression is returned The Filter parameter is a server-side filter for certain subsite properties that are stored in the content database; without the 
Filter parameter, filtering on these properties is a slow process.  These subsite properties are Template and Title. The Filter parameter
 is a script block that uses the same syntax as a Where-Object statement, but is run server-side for faster results It is important to note that every site collection returned by the Get-SPWeb cmdlet is automatically disposed of at the end of th
e pipeline. To store the results of Get-SPWeb in a local variable, the Start-SPAssignment and Stop-SPAssignment cmdlets must be used to a
void memory leaks For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPWeb [[-Identity] <SPWebPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Filter <Script
Block>] [-Limit <String>] [-Regex <SwitchParameter>] [-Site <SPSitePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE 1---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWeb -site http://sitename/sites/site1
]]>
        </Code>
        <Remarks> This example returns all the subwebs in a given site collection </Remarks>
      </example>
      <example>
        <title> --------------------EXAMPLE 2---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWeb -filter {$_.Template -eq "STS#0"}
]]>
        </Code>
        <Remarks> This example displays all subsites that use the "STS#0" template </Remarks>
      </example>
      <example>
        <title> --------------------EXAMPLE 3---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPAssignment -Global

C:\PS>$w = Get-SPWeb http://sitename

C:\PS>$w.set_SiteLogoUrl("http://PathToImage/test.jpg")

C:\PS>$w.Update()

C:\PS>Stop-SPAssignment -Global
]]>
        </Code>
        <Remarks> This example demonstrates how to save a subsite as a variable and to call object model methods on the SPAssignment object </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWebAnalyticsServiceApplication </name>
    <synopsis><![CDATA[ Returns the settings for a Web Analytics Service application. ]]></synopsis>
    <description><![CDATA[ The Get-WebAnalyticsServiceApplication cmdlet reads the settings for a Web Analytics Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http:} } ]]></description>
    <syntax>
      <![CDATA[
Get-SPWebAnalyticsServiceApplication [-Identity] <WebAnalyticsServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection
>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>get-spwebanalyticsserviceapplication WebAnalyticsServiceApplication1
]]>
        </Code>
        <Remarks> This example displays all Web Analytics Service application settings </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWebAnalyticsServiceApplicationProxy </name>
    <synopsis><![CDATA[ Retrieves a new Web Analytics Service application proxy. ]]></synopsis>
    <description><![CDATA[ The Get-SPWebAnalyticsServiceApplicationProxy cmdlet retrieves a Web Analytics Service application proxy from the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http:} } ]]></description>
    <syntax>
      <![CDATA[
Get-SPWebAnalyticsServiceApplicationProxy [-Identity] <WebAnalyticsServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignment
Collection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebAnalyticsServiceApplicationProxy -Identity "WebAnalyticsServiceApp1"
]]>
        </Code>
        <Remarks> This example retrieves settings for the application proxy named WebAnalyticsServiceApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWebApplication </name>
    <synopsis><![CDATA[ Returns all Web applications that match the given criteria. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPWebApplication cmdlet returns all Web applications that match the scope given by the Identity parameter. The Identity c
an be the name of the name, URL, or GUID of the Web application. If no Identity is specified, all Web applications are returned The Central Administration Web application is only returned if its exact identity is provided or the IncludeCentralAdministration
 flag is provided For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPWebApplication [[-Identity] <SPWebApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-IncludeCentralAdministr
ation <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$w = Get-SPWebApplication http://sitename
]]>
        </Code>
        <Remarks> This example gets the Web application for http://sitename and stores it in a variable </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication -IncludeCentralAdministration | Where { $_.DefaultServerComment -eq "SharePoint Central Administration v4"} |
 Format-List *
]]>
        </Code>
        <Remarks> This example displays all public properties on the SharePoint Central Administration Web application in list format </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWebApplicationHttpThrottlingMonitor </name>
    <synopsis><![CDATA[ Returns all counters and their associated Health Score bucket values for network throttling on a Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPWebApplicationHttpThrottlingMonitor cmdlet reads all counters for network throttling on a Web application. This cmdlet 
returns a list that contains all of the performance counters and their associated Health Score bucket values For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPWebApplicationHttpThrottlingMonitor [-Identity] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$s = get-SPWebApplicationHTTPThrottlingMonitors http://sharepoint
]]>
        </Code>
        <Remarks>
          This example gets all performance counters that are being read in the network throttling monitor for the http://sharepoint Web ap
          plication
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWebPartPack </name>
    <synopsis><![CDATA[ Returns the Web Part packages that were installed for the specified scope. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPWebPartPack cmdlet returns the installed Web Part packages that match the Identity parameter. The scope of results can 
be narrowed by using the optional WebApplication parameter. The scope does not include any Web Part packages installed in the global asse
mbly cache (GAC) unless the GlobalOnly parameter is used. If this parameter is used, only Web Part packages that have been installed in t
he GAC are returned For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPWebPartPack [[-Identity] <String>] [-AssignmentCollection <SPAssignmentCollection>] [-GlobalOnly <SwitchParameter>] [-WebApplicati
on <SPWebApplicationPipeBind>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebPartPack -WebApplication http://zsharepoint2:80
]]>
        </Code>
        <Remarks> This example returns all Web Part packages that have been installed on the Web application on port 80 in local farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWebTemplate </name>
    <synopsis><![CDATA[ Displays all globally installed site templates that match the given identity. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPWebTemplate cmdlet displays all installed site templates that match the full or partial identity that was given For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPWebTemplate [[-Identity] <SPWebTemplatePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>$template = Get-SPWebTemplate "STS#0"

C:\PS>New-SPSite http://contoso.com -OwnerAlias "DOMAIN\JDOE" -Template $template
]]>
        </Code>
        <Remarks> This example creates a site collection by using the team site Web template (ID=STS#0) </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebTemplate "STS*"
]]>
        </Code>
        <Remarks> This example displays basic information about all the STS templates </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Get-SPWorkflowConfig </name>
    <synopsis><![CDATA[ Returns workflow settings for the specified Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPWorkflowConfig cmdlet returns workflow settings for the Web application specified by the WebApplication parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Get-SPWorkflowConfig [-WebApplication] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
Get-SPWorkflowConfig [-SiteCollection] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWorkFlowConfig -webapplication http://sitename
]]>
        </Code>
        <Remarks>
          This example gets workflow settings for the specified Web application (http://sitename) To get farm-level workflow settings for event delivery time-out, postpone threshold, and batch size, use the Get-SPFarmConfig cmd
          let
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Grant-SPBusinessDataCatalogMetadataObject </name>
    <synopsis><![CDATA[ Grants a right to a principal for the specified Business Data Connectivity Metadata Store metadata object. ]]></synopsis>
    <description>
      <![CDATA[ The Grant-SPBusinessDataCatalogMetadataObject cmdlet grants the right to a specified principal (user) for a Business Data Connect
ivity Metadata Store metadata object. This cmdlet checks to verify that the Identity parameter is a valid IndividuallySecurableMetadata o
bject For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Grant-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> -Principal <SPClaim> -Right <Execute | Edit | SetPermissions | Sele
ctableInClients> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-SettingId <String>] [-WhatIf [<Switch
Parameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$claimJohn = New-SPClaimObject -User "CONTOSO\johndoe" -Type windowssamaccountname
$Model = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Model" -ServiceContext http://contoso -Name "ContosoModel"
Grant-SPBusinessDataCatalogMetadataObject -Identity $Model -Principal $claimJohn -Right Edit
]]>
        </Code>
        <Remarks>
          This example gives Edit permissions to the user with the identity johndoe on domain CONTOSO, for the model metadata object with t
          he name ContosoModel
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Grant-SPObjectSecurity </name>
    <synopsis><![CDATA[ Adds a new security principal to an SPObjectSecurity object. ]]></synopsis>
    <description>
      <![CDATA[ The Grant-SPObjectSecurity cmdlet adds a new security principal, such as a user, to a SPObjectSecurity object. An SPObjectSecurit
y object is a common object that is used to represent the security access control list (ACL) of SharePoint administrative objects, in par
ticular, service applications For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Grant-SPObjectSecurity [-Identity] <SPObjectSecurity> [-Principal] <SPClaim> [-Rights] <String[]> [-AssignmentCollection <SPAssignmentCo
llection>] [-Replace <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$security = Get-SPServiceApplicationSecurity $serviceApp -Admin
Grant-SPObjectSecurity $security $principal "Full Control"
Set-SPServiceApplicationSecurity $serviceApp -Admin $security
]]>
        </Code>
        <Remarks>
          This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on a service application, and adds a ne
          w user principal to that ACL. The new user is an administrator for the service application $serviceApp
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPBusinessDataCatalogDotNetAssembly </name>
    <synopsis><![CDATA[ Imports a .NET Connectivity assembly. ]]></synopsis>
    <description>
      <![CDATA[ The Import-SPBusinessDataCatalogDotNetAssembly cmdlet imports a .NET Connectivity Assembly that corresponds to a .NET Assembly Co
nnector and LobSystem in the metadata store For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Import-SPBusinessDataCatalogDotNetAssembly -LobSystem <LobSystem> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Conf
irm [<SwitchParameter>]] [-DependentAssemblyPaths <String[]>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE 1---------------- </title>
        <Code>
          <![CDATA[
C:\PS>Import-SPBusinessDataCatalogDotNetAssembly -LobSystem $ContosoDB -Path "c:\Folder\Assembly.dll"
]]>
        </Code>
        <Remarks> This example imports the assembly Assembly </Remarks>
      </example>
      <example>
        <title> -----------------EXAMPLE 2---------------- </title>
        <Code>
          <![CDATA[
C:\PS>Import-SPBusinessDataCatalogDotNetAssembly -LobSystem $ContosoDB -Path "c:\Folder\Assembly.dll" -DependentAssemblyPaths "c:\Folder
\Assembly2.dll","c:\Folder\Assembly3.dll"
]]>
        </Code>
        <Remarks> This example imports the assembly Assembly, and also imports the dependent assemblies Assembly2 and Assembly3 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPBusinessDataCatalogModel </name>
    <synopsis><![CDATA[ Imports a Business Data Connectivity Model. ]]></synopsis>
    <description>
      <![CDATA[ The Import-SPBusinessDataCatalogModel cmdlet imports a Business Data Connectivity Model. There are two types of Business Data Con
nectivity models: Model type (.bdcm) and Resource type (.bdcr). The Model type contains the base XML metadata, and can also include resou
rce properties. The Resource type includes only resource properties For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Import-SPBusinessDataCatalogModel -Identity <MetadataObject> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [
<SwitchParameter>]] [-Force <SwitchParameter>] [-LocalizedNamesIncluded <SwitchParameter>] [-ModelsIncluded <SwitchParameter>] [-Permiss
ionsIncluded <SwitchParameter>] [-PropertiesIncluded <SwitchParameter>] [-SettingId <String>] [-WhatIf [<SwitchParameter>]] [<CommonPara
meters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$MetadataStore = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "Catalog" -ServiceConext http://contoso
Import-SPBusinessDataCatalogModel -Path "C:\folder\model.bdcm" -Identity $MetadataStore
]]>
        </Code>
        <Remarks>
          This example gets the Business Data Connectivity Metadata Store and then imports a Business Data Connectivity Model of Model type
          to it from the path specified with the name model
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPEnterpriseSearchTopology </name>
    <synopsis><![CDATA[ Imports and activates a topology from an XML file. ]]></synopsis>
    <description>
      <![CDATA[ The Import-SPEnterpriseSearchTopology cmdlet imports from an XML file the topology for a shared search application. The Export-SP
EnterpriseSearchTopology cmdlet is used to save a search topology For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Import-SPEnterpriseSearchTopology -Filename <String> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAss
ignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceAplication
Import-SPEnterpriseSearchTopology -SearchApplication $ssa -Filename .\topology.xml
]]>
        </Code>
        <Remarks> This example imports a topology from a file named topology.xml to a search application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPInfoPathAdministrationFiles </name>
    <synopsis><![CDATA[ Imports Microsoft InfoPath 2010 form templates and .udcx files that are located on the SharePoint Central Administration Web site. ]]></synopsis>
    <description>
      <![CDATA[ The Import-SPInfoPathAdministrationFiles cmdlet imports InfoPath 2010 form templates (.xsn files) and universal data connections 
(.udcx files) that are located on the SharePoint Central Administration Web site into the specified InfoPath Forms Services service. This
 cmdlet imports from a backup package that includes all workflow forms in Microsoft InfoPath that were deployed by an administrator and n
ot included with Microsoft SharePoint Foundation 2010, and browser forms that were deployed by an administrator For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Import-SPInfoPathAdministrationFiles -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Id
entity <SPFormsServicePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Import-SPInfoPathAdministrationFiles -path "backupfiles.cab"
]]>
        </Code>
        <Remarks>
          This example imports form templates (XSN files) and universal data connections (UDCX files) located on the SharePoint Central Adm
          inistration Web site into the specified Forms service
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPMetadataWebServicePartitionData </name>
    <synopsis><![CDATA[ Restores the data for a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ Use the Import-SPMetadataWebServicePartitionData cmdlet to restore data for a site subscription to a shared service application f
or the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Import-SPMetadataWebServicePartitionData -Identity <SPSiteSubscriptionPipeBind> -ServiceProxy <SPMetadataServiceProxyCmdletPipeBind> -Pa
th <String> [-AssignmentCollection <SPAssignmentCollection>] [-OverwriteExisting <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Import-SPMetadataWebServicePartitionData -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -Path "\\serve
r_name\folder_name\file_name.cab"
]]>
        </Code>
        <Remarks>
          This example restores a backup of Metadata Service application data for a specific site subscription on a Metadata Service applic
          ation
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPSiteSubscriptionBusinessDataCatalogConfig </name>
    <synopsis>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Import-SPSiteSubscriptionBusinessDataCatalogConfig -Path <String> -ServiceContext <SPServiceContextPipeBind> [-ModelsIncluded] [-Localiz
edNamesIncluded] [-PropertiesIncluded] [-ProxiesIncluded] [-PermissionsIncluded] [-AssignmentCollection <SPAssignmentCollection>] [-Verb
ose] [-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>
] [-OutVariable <String>] [-OutBuffer <Int32>] [-WhatIf] [-Confirm]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPSiteSubscriptionSettings </name>
    <synopsis><![CDATA[ Restores a backup of subscription site settings to the given subscription identifier. ]]></synopsis>
    <description>
      <![CDATA[ The Import-SPSiteSubscriptionSettings cmdlet restores a backup of subscription site settings to the given subscription identifier
 when the Identity parameter is used. To overwrite existing settings, use the Force parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Import-SPSiteSubscriptionSettings [-Identity] <SPSiteSubscriptionPipeBind> -Path <String> [-AdminProperties <SwitchParameter>] [-Assignm
entCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<Common
Parameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscription http://contoso.com | Import-SPSiteSubscriptionSettings -path "c:/backups/contoso_settings_file.bak" -force
]]>
        </Code>
        <Remarks> This example restores the subscription settings store of contoso.com </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Import-SPWeb </name>
    <synopsis><![CDATA[ Imports a site collection, Web application, list, or library. ]]></synopsis>
    <description>
      <![CDATA[ The Import-SPWeb cmdlet imports a site collection, Web application, list, or library. The capability to import from a library is 
a new feature in SharePoint 2010 Products For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Import-SPWeb [-Identity] <SPWebPipeBind> -Path <String> [-ActivateSolutions <SwitchParameter>] [-AssignmentCollection <SPAssignmentColle
ction>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-HaltOnError <SwitchParameter>] [-HaltOnWarning <SwitchParameter>] [-
IncludeUserCustomAction <None | All>] [-IncludeUserSecurity <SwitchParameter>] [-NoFileCompression <SwitchParameter>] [-NoLogFile <Switc
hParameter>] [-UpdateVersions <Append | Overwrite | Ignore>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Import-SPWeb http://site -Path export.cmp -UpdateVersions -Overwrite
]]>
        </Code>
        <Remarks>
          This example imports the contents of export.cmp into a site at http://site, overwriting the versioned content on the site with th
          e contents of the export.cmp file
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Initialize-SPResourceSecurity </name>
    <synopsis><![CDATA[ Enforces resource security on the local server. ]]></synopsis>
    <description>
      <![CDATA[ The Initialize-SPResourceSecurity cmdlet enforces resource security on the local server. This cmdlet enforces security for all re
sources, including files, folders, and registry keys For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Initialize-SPResourceSecurity [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Initialize-SPResourceSecurity
]]>
        </Code>
        <Remarks> This example enforces resource security on the local server </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Initialize-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Installs the state database schema into a state service database. ]]></synopsis>
    <description>
      <![CDATA[ The Initialize-SPStateServiceDatabase cmdlet installs the session state database schema in an empty state service database. The c
urrent user's credentials are used to create the state database schema For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Initialize-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Initialize-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b
]]>
        </Code>
        <Remarks> This example installs the state service database schema into the database associated with the provided identity </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPApplicationContent </name>
    <synopsis><![CDATA[ Copies shared application data to existing Web application folders. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPApplicationContent cmdlet copies shared application data to existing Web application folders This cmdlet does not take any parameters For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPApplicationContent [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPApplicationContent
]]>
        </Code>
        <Remarks> This example copies data to a Web application in the existing folders </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPDataConnectionFile </name>
    <synopsis><![CDATA[ Installs the provided data connection file. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPDataConnectionFile cmdlet installs the provided data connection file. If the specified data connection file exists,
 the user is prompted to replace the existing file This cmdlet does not create a new file. Instead, it creates a new data connection file object For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPDataConnectionFile -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Category <String>] [-Confirm [<SwitchPara
meter>]] [-Overwrite <SwitchParameter>] [-WebAccessible <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPDataConnectionFile -Path .\folder\sample.udcx -Category "Install" -WebAccessible $true

C:\PS>".\folder\sample.udcx" | Install-SPDataConnectionFile -Category "Install" -Category "Category1"  -Overwrite $true
]]>
        </Code>
        <Remarks>
          This example uploads a data connection file to a specified category This cmdlet is equivalent to the Upload Data Connection File user interface setting that is located on the Manage Data Connection
          Files page of the SharePoint Central Administration Web site
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPFeature </name>
    <synopsis><![CDATA[ Installs a SharePoint Feature by using the Feature.xml file. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPFeature cmdlet installs a specific SPFeature object by providing in the Identity parameter the relative path from t
he folder "$env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\ to the feature. The SharePoint Fea
ture's files must already be put in the proper directory, either manually or by using a solution installer If the AllExistingFeatures parameter is provided, the file system is scanned and any new features are installed. This is generall
y only used during deployment and upgrade For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPFeature [-Path] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParame
ter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Install-SPFeature -AllExistingFeatures <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]]
 [-Force <SwitchParameter>] [-SolutionId <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Install-SPFeature -ScanForFeatures <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-F
orce <SwitchParameter>] [-SolutionId <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPFeature -path "MyCustomFeature"
]]>
        </Code>
        <Remarks>
          This example installs a new feature at $env:ProgramFiles\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES
          \MyCustomFeature/feature.xml
        </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPFeature -AllExistingFeatures -Whatif
]]>
        </Code>
        <Remarks>
          This example shows the unregistered features, available on the file system, that are installed if this command is run without the
          WhatIf parameter. This is commonly done after an upgrade process
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPHelpCollection </name>
    <synopsis><![CDATA[ Installs the provided Help site collection files in the current farm. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPHelpCollection cmdlet installs the Help site collection files for SharePoint 2010 Products in the current farm. Use
 the LiteralPath parameter to install specific custom Help collection files. If the LiteralPath parameter is not specified, all available
 Help in the Help site collection is installed and existing Help collection files are overwritten For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPHelpCollection -LiteralPath <String> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
Install-SPHelpCollection -All <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPHelpCollection -LiteralPath 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\HCCab\1033\OSSAdmin
.cab'
]]>
        </Code>
        <Remarks> This example installs the specified help collection in the current farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPService </name>
    <synopsis><![CDATA[ Installs and provisions services on a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPService cmdlet installs and optionally provisions services on a farm. This cmdlet installs all services, service in
stances, and service proxies specified in the registry on the local server computer. Use this cmdlet in a script that you build to instal
l and deploy a SharePoint farm or to install a custom developed service For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPService [-AssignmentCollection <SPAssignmentCollection>] [-Provision <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPService
]]>
        </Code>
        <Remarks>
          This example installs all services, service instances and service proxies specified in the registry on the local server computer.
          } }
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPSolution </name>
    <synopsis><![CDATA[ Deploys an installed SharePoint solution in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPSolution cmdlet deploys an installed SharePoint solution in the farm. Use the Add-SPSolution cmdlet to install a Sh
arePoint solution package io the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPSolution [-Identity] <SPSolutionPipeBind> [-AllWebApplications <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollecti
on>] [-CASPolicies <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-GACDeployment <SwitchParameter>] [-Lan
guage <UInt32>] [-Local <SwitchParameter>] [-Time <String>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [
<CommonParameters>]
Install-SPSolution [[-Identity] <SPSolutionPipeBind>] -Synchronize <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-Language <UInt32>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPSolution -Identity contoso_solution.wsp -GACDeployment
]]>
        </Code>
        <Remarks>
          This example deploys the installed SharePoint solution contoso_solution.wsp in the farm and specifies that GAC can be deployed fo
          r the new SharePoint solution
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPUserSolution </name>
    <synopsis><![CDATA[ Activates a sandboxed solution in a site collection. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPUserSolution cmdlet activates a sandboxed solution in a site collection. A user solution is a sandboxed solution For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPUserSolution [-Identity] <SPUserSolutionPipeBind> -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Co
nfirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPUserSolution -Identity contoso_solution.wsp -Site http://sitename
]]>
        </Code>
        <Remarks> This example activates the sandboxed solution contoso_solution.wsp in the site http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPWebPartPack </name>
    <synopsis><![CDATA[ Installs the specified Web Part package to the specified location. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPWebPartPack cmdlet installs the Web Part package, at the LiteralPath parameter location, in the local farm. The Web
 Part package can be installed in a specific Web application by using the WebApplication parameter. If a Web application is not specified
, the Web Part package is installed in all Web applications Use the Language parameter to specify a package language Use the GlobalInstall parameter to install the package to the global assembly cache (GAC). Assemblies in the GAC are granted Full
Trust permission, which gives this package full access to all system-wide resources Use the Force parameter to install the package to overwrite any existing Web Part package with the same name or installed in the 
same location For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPWebPartPack [-LiteralPath] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <S
witchParameter>] [-GlobalInstall <SwitchParameter>] [-Language <UInt32>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf [<SwitchP
arameter>]] [<CommonParameters>]
Install-SPWebPartPack [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchPa
rameter>] [-GlobalInstall <SwitchParameter>] [-Language <UInt32>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf [<SwitchParamete
r>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPWebPartPack "MyCustomWebPartPack" -LiteralPath "c:/mywebpart.wpp" -GlobalInstall
]]>
        </Code>
        <Remarks>
          This example installs the Web Part Package with the name MyCustomWebPartPack globally in the farm from the path c:/mywebpart.wpp.
          } }
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Install-SPWebTemplate </name>
    <synopsis><![CDATA[ Installs the given site template. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPWebTemplate cmdlet installs the given site template using the name provided (title) as the unique ID For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Install-SPWebTemplate [-Path] <String> -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-
Description <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Install-SPSiteTemplate -path "mytemplate.cab" -name "My Template" -description "TestFarm"
]]>
        </Code>
        <Remarks> This example installs the mytemplate.cab file as My Template with the description "TestFarm" on the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Merge-SPLogFile </name>
    <synopsis><![CDATA[ Combines trace log entries from all farm computers into a single log file on the local computer. ]]></synopsis>
    <description>
      <![CDATA[ The Merge-SPLogFile cmdlet returns records from Unified Logging Service (ULS) trace log files on each farm server that match the 
criteria, and writes the results to a new log file on the local computer. If no results are returned, a warning is written to the Windows
 PowerShell console window We recommend that you filter by using the StartTime and EndTime parameters to optimize performance of this cmdlet. Some filtering
 parameters such as Process, Area, Category, EventID and Message support wildcards For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Merge-SPLogFile -Path <String> [-Area <String[]>] [-AssignmentCollection <SPAssignmentCollection>] [-Category <String[]>] [-ContextFilte
r <String[]>] [-Correlation <Guid[]>] [-EndTime <DateTime>] [-EventID <String[]>] [-ExcludeNestedCorrelation <SwitchParameter>] [-Level 
<String>] [-Message <String[]>] [-Overwrite <SwitchParameter>] [-Process <String[]>] [-StartTime <DateTime>] [-ThreadID <UInt32[]>] [<Co
mmonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite
]]>
        </Code>
        <Remarks> This example merges the last hour of log data from all farm computers with no filtering </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Area Search
]]>
        </Code>
        <Remarks> This example merges the last hour of log data from the Search area </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Area "SharePoint Foundation","Web Analytics Services"
]]>
        </Code>
        <Remarks> This example merges the last hour of log data from the SharePoint Foundation and Web Analytics Services areas </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 4----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Level High
]]>
        </Code>
        <Remarks> This example merges the log data of level High or higher </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 5----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -StartTime "06/09/2008 16:00" - EndTime "06/09/2008 16:15"
]]>
        </Code>
        <Remarks> This example merges the log data for events in a particular time range, which is culture-specific to the United States </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 6----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Path "C:\Logs\FarmMergedLog.log" -Overwrite -Message "*permission changed*"
]]>
        </Code>
        <Remarks> This example merges the log data for events with permission changed in the message text </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 7----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Overwrite -Path d:\1.log -ContextFilter "name=timer job*" -Area "*search*"
]]>
        </Code>
        <Remarks> This example merges the log data for all search timer jobs </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 8----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Merge-SPLogFile -Overwrite -Path d:\2.log -ContextFilter "user=contoso?joeuser"
]]>
        </Code>
        <Remarks> This example shows how to merge the log data for all user names that have a contoso\joeuser or Contoso/joeuser format </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Mount-SPContentDatabase </name>
    <synopsis><![CDATA[ Attaches an existing content database to the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Mount-SPContentDatabase cmdlet attaches an existing content database to the farm. If the database being mounted requires an u
pgrade, this cmdlet will cause the database to be upgraded For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Mount-SPContentDatabase [-Name] <String> [-WebApplication] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [
-AssignNewDatabaseId <SwitchParameter>] [-ClearChangeLog <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCred
ential>] [-DatabaseServer <String>] [-MaxSiteCount <Int32>] [-UpdateUserExperience <SwitchParameter>] [-WarningSiteCount <Int32>] [-What
If [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Mount-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename
]]>
        </Code>
        <Remarks> This example mounts an already existing database to the sitename Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Mount-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Attaches an existing state service database to the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Mount-SPStateServiceDatabase cmdlet attaches an existing state service database to the farm. If the session state database sc
hema is not installed in the state service database, use the Initialize-SPStateServiceDatabase cmdlet to install the schema after the sta
te service database has been mounted For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Mount-SPStateServiceDatabase [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseCredentials <PSCredential>] [-D
atabaseServer <String>] [-ServiceApplication <SPStateServiceApplicationPipeBind>] [-Weight <Nullable>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Mount-SPStateServiceDatabase -Name "statedata1" -DatabaseServer "localhost"
]]>
        </Code>
        <Remarks>
          This example associates a Microsoft SharePoint Server 2010 farm with a SQL Server database This example is used in least privilege scenarios when an administrator cannot create databases in SQL. The database must already
          exist and be empty. The database cannot be used until the Initialize-SPStateServiceDatabase cmdlet is run, so errors could occur with th
          is example
        </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Mount-SPStateServiceDatabase -Name "statedata1" -DatabaseServer "localhost" -ServiceApplication "ServiceApp1" -Weight 10 | Initial
ize-SPStateServiceDatabase
]]>
        </Code>
        <Remarks>
          This example associates a Microsoft SharePoint Server 2010 farm with a SQL Server database, at the same time that it also associa
          tes the database with a service application and gives a weight of 10. The result is immediately piped to the Initialize-SPStateServiceDat
          abase cmdlet so that the database can be used
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Move-SPBlobStorageLocation </name>
    <synopsis><![CDATA[ Copies a Windows SharePoint Services 3.0 database by using Remote BLOB Storage (RBS). ]]></synopsis>
    <description>
      <![CDATA[ Use the Move-SPBlobStorageLocation cmdlet to copy a Windows SharePoint Services 3.0 database into a Microsoft SQL Server 2008 wit
h Service Pack 1 (SP1) database instance by using Remote BLOB Storage (RBS). The database size limitation for SQL Server 2008 with SP1 is
 4 gigabyes (GB). If a Windows SharePoint Services 3.0 database is greater than 4 GB, the database cannot be copied directly into a SQL S
erver 2008 with SP1 database instance. The Move-SPBlobStorageLocation cmdlet uses the advantage of RBS and copies databases larger than 4
 GB. RBS stores the data on the local hard disk and keeps the links to the data in the database, which results in a smaller database For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Move-SPBlobStorageLocation [-SourceDatabase] <String> [-AssignmentCollection <SPAssignmentCollection>] [-BackupDatabase <String>] [-Back
upFileName <String>] [-Confirm [<SwitchParameter>]] [-DebugMod <$true | $false>] [-DestDatabaseFilesBaseName <String>] [-DestinationData
base <String>] [-DestinationDataSourceInstance <String>] [-Dir <String>] [-MasterPassword <String>] [-VerboseMod <$true | $false>] [-Wha
tIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Move-SPBlobStorageLocation WSS_Content
]]>
        </Code>
        <Remarks>
          This example copies the content database named WSS_Content from the Windows Internal Database to the same database name in Micros
          oft SQL Server 2008 Express by using RBS
        </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Move-SPBlobStorageLocation WSS_Content -DestinationDatabase WSS_V4_Content -BackupDatabase WSSBackupDB -VerboseMod:$true
]]>
        </Code>
        <Remarks>
          This example copies the content database named WSS_Content from the Windows Internal Database to a database in SQL Server 2008 Ex
          press. The name of the new database will be WSS_V4_Content. During the move, the backup file name will be WSSBackupDB. The output of this
          command displays log information to the Command Prompt window
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Move-SPProfileManagedMetadataProperty </name>
    <synopsis><![CDATA[ Moves multiple-string values into a term set. ]]></synopsis>
    <description>
      <![CDATA[ Use the Move-SPProfileManagedMetadataProperty cmdlet to move multiple-string or single-string property values into a term set tha
t you specify. If you do not specify a term set, the values are moved into the Keywords term set. Any new values you add to the property 
after running the cmdlet will be moved into the term set that you specified After a user profile application has been upgraded from Microsoft Office SharePoint Server 2007, single-string and multiple-strin
g value properties are not available for use unless the Move-SPProfileManagedMetadataProperty cmdlet is run to map them to term sets with
in Managed Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Move-SPProfileManagedMetadataProperty -Identity <String> -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-Assignmen
tCollection <SPAssignmentCollection>] [-AvailableForTagging <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-TermSetName <String>] [-
WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Move-SPProfileManagedMetadataProperty -Identity SPS-Interests -TermSetName Interests -AvailableForTagging -ProfileServiceApplicati
onProxy dbc4ccf5-b245-4e0f-8696-235402f83260
]]>
        </Code>
        <Remarks>
          This example moves values from the SPS-Interests property into a new term set called Interests, and marks that term set as availa
          ble for tagging
        </Remarks>
      </example>
      <example>
        <title> ---------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplicationProxy | ?{$_.DisplayName.Contains("User Profile Service")} | Move-SPProfileManagedMetadataProperty -Identi
ty SPS-Interests -TermSetName Interests -AvailableForTagging
]]>
        </Code>
        <Remarks>
          This example performs the same task as Example 1, but pipes the result for the ProfileServiceApplicationProxy parameter by using
          the Get-SPServiceApplicationProxy cmdlet
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Move-SPSite </name>
    <synopsis><![CDATA[ Moves site collections from one content database to another. ]]></synopsis>
    <description>
      <![CDATA[ The Move-SPSite cmdlet moves the data in the specified site collection from its current content database to the content database 
specified by the DestinationDatabase parameter. A read-only lock is applied to the site collection to prevent users from altering data wi
thin the site collection while the move is taking place. Once the move is complete, the site collection is returned to its original lock 
state.  The destination content database specified must already exist, must be attached to the same SQL Server as the site collection's c
urrent content database, and must be attached to the site collection's current Web application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Move-SPSite [-Identity] <SPSitePipeBind> -DestinationDatabase <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection
>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Move-SPSite http://servername/sites/sitename -DestinationDatabase ContentDb2
]]>
        </Code>
        <Remarks> This example moves the site collection http://servername/sites/sitename to the content database ContentDb2 </Remarks>
      </example>
      <example>
        <title> ---------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite -ContentDatabase ContentDb1 | Move-SPSite -DestinationDatabase ContentDb2
]]>
        </Code>
        <Remarks> This example moves all site collections in ContentDb1 to ContentDb2 </Remarks>
      </example>
      <example>
        <title> ---------------------EXAMPLE 3----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteAdministration | where { $_.OwnerLoginName -eq "DOMAIN\username" } | Move-SPSite -DestinationDatabase ContentDb2
]]>
        </Code>
        <Remarks>
          This example moves all site collections where DOMAIN\username is the site collection owner to ContentDb2. The Get-SPSiteAdministr
          ation cmdlet is used instead of the Get-SPSite cmdlet because you must have permission within the site collection to access the propertie
          s of the SPSite object. You can access the properties of the SPSiteAdministration object as a SharePoint farm administrator
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Move-SPUser </name>
    <synopsis><![CDATA[ Migrates a user account in SharePoint 2010 Products. ]]></synopsis>
    <description>
      <![CDATA[ The Move-SPUser cmdlet migrates user access from one domain user account to another. If an entry for the new login name already e
xists, the entry is marked for deletion to make way for the migration For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Move-SPUser [-Identity] <SPUserPipeBind> -NewAlias <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter
>]] [-IgnoreSID <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Move-SPUser -Identity "DOMAIN\JaneDoe" -NewAlias "Domain\JaneSmith"
]]>
        </Code>
        <Remarks> This example migrates DOMAIN\JaneDoe to the new account of DOMAIN\JaneSmith </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPAlternateURL </name>
    <synopsis><![CDATA[ Creates a new public or internal URL for the specified Web application zone or resource. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPAlternateUrl cmdlet creates a new public or internal URL for the specified Web application zone or resource. Use the Re
sourceName parameter if the alternate URL is for an external resource Each Web application can be associated with a collection of mappings between internal and public URLs. Both internal and public U
RLs consist of the protocol and domain portion of the full URL; for example, https://www.fabrikam.com. Users type a public URL to get to 
the SharePoint site, and that URL appears in the links on the pages. Internal URLs are in the URL requests that are sent to the SharePoin
t site. Many internal URLs can be associated with a single public URL in multiserver farms; for example, when a load balancer routes requ
ests to specific IP addresses to various servers in the load-balancing cluster Each Web application supports five collections of mappings per URL; the five collections correspond to five zones (default, intra
net, extranet, Internet, and custom). When the Web application receives a request for an internal URL in a particular zone, links on the 
pages returned to the user have the public URL for that zone For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPAlternateUrl [-Url] <String> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm
 [<SwitchParameter>]] [-Internal <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [-Zone <Default | Intranet | Internet | Custom | Extra
net>] [<CommonParameters>]
New-SPAlternateUrl [-Url] <String> -ResourceName <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]
] [-Internal <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [-Zone <Default | Intranet | Internet | Custom | Extranet>] [<CommonParame
ters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>#create the public URL
New-SPAlternateURL https://www.contoso.com -Zone "Internet"

C:\PS>#create the internal URL
New-SPAlternateURL http://sharepoint.contoso.com -Zone "Internet" -internal
]]>
        </Code>
        <Remarks>
          This example translates incoming requests for https://www.contoso.com into http://sharepoint.contoso.com (on the Internet zone) When a reverse proxy is being set up to handle public URL SSL termination, alternate access mappings must be configured to handle
          the URL translation
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPAuthenticationProvider </name>
    <synopsis><![CDATA[ Creates a new Authentication provider in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPAuthenticationProvider cmdlet creates a new Authentication provider in the farm NTLM, Classic NTLM, Negotiate, and Classic Negotiate can be set only in a Web Application For ASP.NET Membership Provider or Role providers, no objects are persisted. The object is created and used for setting this type
 of Authentication provider in a Web application For STS Authentication providers, an object is created and persisted in the SPFarm object Using classic NTLM with any claims based authentication type is not allowed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPAuthenticationProvider [-AllowAnonymous <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [-DisableKerberos <Swi
tchParameter>] [-UseBasicAuthentication <SwitchParameter>] [-UseWindowsIntegratedAuthentication <SwitchParameter>] [<CommonParameters>]
New-SPAuthenticationProvider -ASPNETMembershipProvider <String> -ASPNETRoleProviderName <String> [-AssignmentCollection <SPAssignmentCol
lection>] [<CommonParameters>]
New-SPAuthenticationProvider -TrustedIdentityTokenIssuer <SPTrustedIdentityTokenIssuerPipeBind> [-AssignmentCollection <SPAssignmentColl
ection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------------EXAMPLE1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ap = New - SPAuthenticationProvider -UseWindowsIntegratedAuthentication

C:\PS>Set-SPWebApplication -Name "Claims Windows Web App" -ApplicationPool "Claims App Pool" -ApplicationPoolAccount "redmond\appool" -U
rl http://servername -Port 80 -AuthenticationProvider $ap
]]>
        </Code>
        <Remarks> This example creates a Windows-claims authentication provider} } </Remarks>
      </example>
      <example>
        <title> ---------------------------EXAMPLE2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ap = New-SPAuthenticationProvider -ASPNETMembershipProvider "membership" -ASPNETRoleProviderName "rolemanager"

C:\PS>Set-SPWebApplication -Name "Claims Windows Web App" -ApplicationPool "Claims App Pool" -ApplicationPoolAccount "redmond\appool" -U
rl http://servername -Port 80 -AuthenticationProvider $ap
]]>
        </Code>
        <Remarks> This example creates an ASP.net membership role provider authentication provider </Remarks>
      </example>
      <example>
        <title> ---------------------------EXAMPLE3------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ap = New - SPAuthenticationProvider -TrustedIdentityTokenIssuer | Get-SPTrustedIdentityTokenIssuer "LiveIDSTS"

C:\PS>Set-SPWebApplication -Name "Claims Windows Web App" -ApplicationPool "Claims App Pool" -ApplicationPoolAccount "redmond\appool" -U
rl http://servername -Port 80 -AuthenticationProvider $ap
]]>
        </Code>
        <Remarks> This example creates a trusted token issuer authentication provider </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPBusinessDataCatalogServiceApplication </name>
    <synopsis><![CDATA[ Creates a new Business Data Connectivity service application in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPBusinessDataCatalogServiceApplication cmdlet creates a new Business Data Connectivity service application in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPBusinessDataCatalogServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignme
ntCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabasePassword <SecureS
tring>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] [-Name <String>] [-PartitionMode <Swi
tchParameter>] [-Sharing <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPBusinessDataCatalogServiceApplication -ApplicationPool "SharePoint Web Services Default" -DatabaseName "ContosoBdcDB" -Datab
aseServer "CONTOSO\SharePoint" -Name "ContosoServiceApp"
]]>
        </Code>
        <Remarks>
          This example creates a Business Data Connectivity service application named ContosoServiceApp. In this process it uses the ShareP
          oint Web Services Default application pool and creates a database named ContosoBdcDB
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPBusinessDataCatalogServiceApplicationProxy </name>
    <synopsis><![CDATA[ Creates a new Business Data Connectivity service application proxy in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPBusinessDataCatalogServiceApplicationProxy cmdlet creates a new Business Data Connectivity service application proxy fo
r a Business Data Connectivity service application in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPBusinessDataCatalogServiceApplicationProxy -Uri <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter
>]] [-DefaultProxyGroup <SwitchParameter>] [-Name <String>] [-PartitionMode <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonPar
ameters>]
New-SPBusinessDataCatalogServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignment
Collection>] [-Confirm [<SwitchParameter>]] [-DefaultProxyGroup <SwitchParameter>] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPBusinessDataCatalogServiceApplicationProxy -Name "ContosoServiceAppProxy" -ServiceApplication $serviceApplication
]]>
        </Code>
        <Remarks>
          This example creates a new Business Data Connectivity service application proxy with the name ContosoServiceAppProxy for the give
          n service application
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPCentralAdministration </name>
    <synopsis><![CDATA[ Creates a new SharePoint Central Administration Web application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPCentralAdministration cmdlet creates a new Central Administration Web application and starts the central administration
 service on the local machine. Central Administration is available only on computers where this service runs For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPCentralAdministration [[-Port] <Int32>] [[-WindowsAuthProvider] <String>] [-AssignmentCollection <SPAssignmentCollection>] [<Commo
nParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPCentralAdministration -Port 3000
]]>
        </Code>
        <Remarks> This example creates the Central Administration site at port 3000 on the local farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPClaimProvider </name>
    <synopsis><![CDATA[ Registers a new claim provider in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPClaimProvider cmdlet registers a new claim provider in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPClaimProvider -AssemblyName <String> -Description <String> -DisplayName <String> -Type <String> [-AssignmentCollection <SPAssignme
ntCollection>] [-Default <SwitchParameter>] [-Enabled <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New - SPClaimProvider -Name "MyClaimProvider" -Type "MyClaimProvider.Providers.CustomProvider" -AllWebApplications
]]>
        </Code>
        <Remarks> This example registers a claim provider in the farm </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New - SPClaimProvider -Name "MyClaimProvider" -Type "MyClaimProvider.Providers.CustomProvider" -Scope (get-SPWebApplication http:/
/office)
]]>
        </Code>
        <Remarks> This example registers a claim provider scoped to a given Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPClaimsPrincipal </name>
    <synopsis><![CDATA[ Creates a claims principal. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPClaimsPrincipal cmdlet creates a claims principal For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPClaimsPrincipal [-Identity] <String> [-IdentityType] <WindowsSamAccountName | WindowsSecurityGroupName | WindowsSecurityGroupSid |
 FormsUser | FormsRole | EncodedClaim> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
New-SPClaimsPrincipal [-Identity] <String> [-TrustedIdentityTokenIssuer] <SPTrustedIdentityTokenIssuerPipeBind> [-AssignmentCollection <
SPAssignmentCollection>] [<CommonParameters>]
New-SPClaimsPrincipal [-ClaimValue] <String> [[-ClaimType] <String>] [-TrustedIdentityTokenIssuer] <SPTrustedIdentityTokenIssuerPipeBind
> [[-IdentifierClaim] <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
New-SPClaimsPrincipal [-EncodedClaim] <String> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]
New-SPClaimsPrincipal [-ClaimValue] <String> [-ClaimType] <String> [-ClaimProvider] <SPClaimProvider> [-AssignmentCollection <SPAssignme
ntCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------------EXAMPLE 1----------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSite http://sitename/sites/newsite -owner (New-SPClaimsPrincipal contoso\johndoe -IdentityProvider "NTLM")
]]>
        </Code>
        <Remarks> This example creates a claim principal for a Windows user </Remarks>
      </example>
      <example>
        <title> -------------------------EXAMPLE 2----------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSite http://localhost/sites/newsite -owner (New-SPClaimsPrincipal contoso\allusers -IdentityProvider "NTLM")
]]>
        </Code>
        <Remarks> This example creates a claim principal for a Windows group </Remarks>
      </example>
      <example>
        <title> -------------------------EXAMPLE 3----------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSite http://sitename/sites/newsite -owner (New-SPClaimsPrincipal -ClaimValue "john@contoso.com" -ClaimType Email -IdentityPr
ovider "LiveID STS" -IdentifierClaim Yes)
]]>
        </Code>
        <Remarks> This example creates a claim principal for a trusted identity token issuer claim </Remarks>
      </example>
      <example>
        <title> -------------------------EXAMPLE 4----------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$ip = New-SPIdentityProvider -ASPNetMembershipProvider "myMembershipProvider" -ASPNetRoleProvider "myRoleProvider"

C:\PS>New-SPSite http://sitename/sites/newsite -owner (New-SPClaimsPrincipal "john@contoso.com" -IdentityProvider $ip)
]]>
        </Code>
        <Remarks> This example creates a claim principal for a ASPNet Membership User </Remarks>
      </example>
      <example>
        <title> -------------------------EXAMPLE 5----------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSite http://sitename/sites/newsite -owner (New-SPClaimsPrincipal "Sales Manager Role" -IdentityProvider "myRoleProvider")
]]>
        </Code>
        <Remarks> This example creates a claim principal for a ASPNet Role </Remarks>
      </example>
      <example>
        <title> -------------------------EXAMPLE 6----------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSite http://sitename/sites/newsite -owner (New-SPClaimsPrincipal "i:xxx|xxxx|contoso\user")
]]>
        </Code>
        <Remarks> This example creates a claim principal for a Basic Claim Role, which is also called an encoded claim) </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPClaimTypeMapping </name>
    <synopsis><![CDATA[ Creates a claim mapping rule for a security token service (STS) identity provider. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPClaimTypeMapping cmdlet creates a claim mapping rule for a security token service (STS) identity provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPClaimTypeMapping [-IncomingClaimType] <String> [-IncomingClaimTypeDisplayName] <String> [[-LocalClaimType] <String>] [-AssignmentC
ollection <SPAssignmentCollection>] [-SameAsIncoming <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE 1---------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$map1 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress" -IncomingCl
aimTypeDisplayName "EmailAddress" -SameAsIncoming

C:\PS>$map2 = New-SPClaimTypeMapping -IncomingClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier" -Incoming
ClaimTypeDisplayName "PUID" -LocalClaimType "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/thumbprint"

C:\PS>New-SPTrustedIdentityTokenIssuer -Name "LiveIDSTS" -Description "LiveID Provider" -Realm "urn:domain.company.com" -ImportTrustCert
ificate $cert -ClaimsMappings $map1[,$map2..] -SignInUrl "https://login.live.com/login.srf" -IdentifierClaim $map2.InputClaimType
]]>
        </Code>
        <Remarks> This example creates a claim map from an incoming token to a SharePoint token </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPConfigurationDatabase </name>
    <synopsis><![CDATA[ Creates a new configuration database. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPConfigurationDatabase cmdlet creates a new configuration database on the specified database server. This is the central
 database for a new SharePoint farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPConfigurationDatabase [-DatabaseName] <String> [-DatabaseServer] <String> [[-DirectoryDomain] <String>] [[-DirectoryOrganizationUn
it] <String>] [[-AdministrationContentDatabaseName] <String>] [[-DatabaseCredentials] <PSCredential>] [-FarmCredentials] <PSCredential> 
[-Passphrase] <SecureString> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPConfigurationDatabase -DatabaseName "SharePointConfigDB1" -DatabaseServer "SQL-01" -Passphrase (ConvertTo-SecureString "MyPa
ssword" -AsPlainText -force) -FarmCredentials (Get-Credential)
]]>
        </Code>
        <Remarks> This example prompts the user to provide user credentials for the default Farm Administrator account </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPContentDatabase </name>
    <synopsis><![CDATA[ Creates a new content database and attaches it to the specified Web application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPContentDatabase cmdlet creates a new content database and attaches it to the specified Web application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPContentDatabase [-Name] <String> [-WebApplication] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-A
ssignNewDatabaseId <SwitchParameter>] [-ClearChangeLog <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCreden
tial>] [-DatabaseServer <String>] [-MaxSiteCount <Int32>] [-WarningSiteCount <Int32>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPContentDatabase "MyDatabase" -DatabaseServer "MyServer" -WebApplication http://sitename
]]>
        </Code>
        <Remarks> This example creates a new content database for the sitename Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPContentDeploymentJob </name>
    <synopsis><![CDATA[ Creates a content deployment job. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPContentDeploymentJob cmdlet adds a new content deployment job to a farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPContentDeploymentJob -Name <String> -SPContentDeploymentPath <SPContentDeploymentPathPipeBind> [-AssignmentCollection <SPAssignmen
tCollection>] [-Confirm [<SwitchParameter>]] [-Description <String>] [-EmailAddresses <String[]>] [-EmailNotifications <None | SendEmail
OnFailure | SendEmailOnSuccess | SendEmailOnAlways>] [-HostingSupportEnabled <SwitchParameter>] [-IncrementalEnabled <SwitchParameter>] 
[-Schedule <String>] [-ScheduleEnabled <SwitchParameter>] [-Scope <SPWebPipeBind[]>] [-SqlSnapshotSetting <None | CreateNew>] [-WhatIf [
<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDeploymentPath "Path 1" | New-SPContentDeploymentJob -Name "Deployment Job" -SPContentDeploymentPath $_ -IncrementalE
nabled:$true -ScheduleEnabled:$false
]]>
        </Code>
        <Remarks>
          This example creates a new content deployment job called Deployment Job by using the deployment path Path 1. The job is configure
          d to be an incremental job with no schedule
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPContentDeploymentPath </name>
    <synopsis><![CDATA[ Creates a new content deployment path. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPContentDeploymentPath cmdlet adds a new content deployment path for a content deployment job For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPContentDeploymentPath -DestinationCentralAdministrationURL <Uri> -DestinationSPSite <String> -DestinationSPWebApplication <Uri> -N
ame <String> -PathAccount <PSCredential> -SourceSPSite <SPSitePipeBind> -SourceSPWebApplication <SPWebApplicationPipeBind> [-AssignmentC
ollection <SPAssignmentCollection>] [-Authentication <Basic | Windows>] [-CompressionEnabled <SwitchParameter>] [-Confirm [<SwitchParame
ter>]] [-DeploySecurityInformation <None | WssOnly | All>] [-DeployUserNamesEnabled <SwitchParameter>] [-Description <String>] [-EventRe
ceiversEnabled <SwitchParameter>] [-KeepTemporaryFilesOptions <Never | Always | Failure>] [-PathEnabled <SwitchParameter>] [-WhatIf [<Sw
itchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$source = Get-SPSite "http://source/"

C:\PS>$credentials=Get-Credential

C:\PS>New-SPContentDeploymentPath -Name "Deployment Path" -SourceSPWebApplication $source.WebApplication -SourceSPSite $source Destinati
onCentralAdministrationURL "http://destination:8080" -DestinationSPWebApplication "http://destination" -DestinationSPSite "http://destin
ation" -KeepTemporaryFilesOptions "Failure" -PathAccount $credentials -PathEnabled:$true
]]>
        </Code>
        <Remarks>
          This example creates a new deployment path called Deployment Path that connects a source at http://source to a destination at htt
          p://destination. The path is enabled and configured to keep temporary files on job failure
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlComponent </name>
    <synopsis><![CDATA[ Creates a crawl component for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlComponent cmdlet is run when the search functionality is initially configured, or when a new crawl
 component is added to a crawl topology for a shared search application. A crawl topology can contain multiple crawl components For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlComponent -CrawlDatabase <CrawlStorePipeBind> -CrawlTopology <CrawlTopologyPipeBind> -SearchServiceInstance <
SearchServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-IndexLocation <String>]
 [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$topo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -Identity 00000000-0000-0000-0000-000000000000
New-SPEnterpriseSearchCrawlComponent -SearchApplication $searchapp -CrawlTopology $topo -CrawlDatabase "Sample_Search_Service_Applicatio
n_CrawlStoreDB" -SearchServiceInstance servername -IndexLocation d:\crawlshare
$topo | Set-SPEnterpriseSearchCrawlTopology -Active
]]>
        </Code>
        <Remarks> This example retrieves the inactive crawl topology, adds a component, and then activates the topology </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlContentSource </name>
    <synopsis><![CDATA[ Creates a new crawl content source for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlContentSource cmdlet creates a new content source For permissions and the most current information about search cmdlets, see the online documentation (http://go.microsoft.com/fwli
nk/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlContentSource [-Name] <String> -SearchApplication <SearchServiceApplicationPipeBind> -Type <Business | O12Bus
iness | CustomRepository | Custom | Exchange | File | LotusNotes | SharePoint | Web> [-AssignmentCollection <SPAssignmentCollection>] [-
BDCApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm [<SwitchParameter>]] [-CrawlPriority <Nullable>] [-CustomPr
otocol <String>] [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Nullable>] [-MaxSiteEnumerationDepth <Nullable>] [-SharePointCraw
lBehavior <Nullable>] [-StartAddresses <String>] [-Tag <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
New-SPEnterpriseSearchCrawlContentSource -SearchApplication $searchapp -Type file -name somename -StartAddresses file://someserver/publi
c
]]>
        </Code>
        <Remarks>
          This example creates a new content source of type file to crawl a file system A crawl schedule must be created by using the Set-SPEnterpriseSearchCrawlContentSource cmdlet to automatically crawl this content
          source
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlCustomConnector </name>
    <synopsis><![CDATA[ Registers a protocol for custom crawling. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlCustomConnector cmdlet registers, for a search system, the protocol that is used to crawl the cust
om repository If the Name parameter is not provided, in the administration application user interface (UI) the name protocol identifies the pro
tocol specified For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlCustomConnector -ModelFilePath <String> -Protocol <String> -SearchApplication <SearchServiceApplicationPipeBi
nd> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<Com
monParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp
New-SPEnterpriseSearchCrawlCustomConnector -SearchApplication $searchApp 
-ModelFilePath \\models\myFileTypeModel.mft -Protocol "mftml://"
]]>
        </Code>
        <Remarks>
          This example creates a custom connector for a file type whose model is located at \\models\myFileTypeModel.mft and has the protoc
          ol name mftml://
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlDatabase </name>
    <synopsis><![CDATA[ Creates a crawl database which can be added to a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlDatabase cmdlet is used during initial configuration and farm scale-out to create a new crawl data
base, which can be added to a search service application. A crawl database stores crawl history for a search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlDatabase -DatabaseName <String> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection 
<SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsernam
e <String>] [-Dedicated <SwitchParameter>] [-FailoverDatabaseServer <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp
New-SPEnterpriseSearchCrawlDatabase -SearchApplication $searchApp 
-DatabaseName newCrawlDB
]]>
        </Code>
        <Remarks> This example creates a new crawl database named newCrawlDB for the mySearchServiceApp search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlExtension </name>
    <synopsis><![CDATA[ Adds an extension rule to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlExtension cmdlet adds a file extension to the list of file types to be included in the index. Run 
this cmdlet after any new IFilter interface is added in order to ensure the new file type is crawled For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlExtension [[-Name] <String>] -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SP
AssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$searchapp | New-SPEnterpriseSearchCrawlExtension "pdf"
]]>
        </Code>
        <Remarks> This example adds, after adding a PDF IFilter, the file type to the list of file extensions to be included in the index </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlMapping </name>
    <synopsis><![CDATA[ Creates a crawl mapping rule for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlMapping cmdlet is run when the search functionality is initially configured, and when access is ch
anged through a different mechanism to create the crawl mapping rule; for example, when a rule is changed to use file:\\ rather than  htt
p:// For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlMapping [-Url] <String> -SearchApplication <SearchServiceApplicationPipeBind> -Target <String> [-AssignmentCo
llection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
New-SPEnterpriseSearchCrawlMapping -SearchApplication $searchapp -Url "file://location1" -Target "http://location2"
]]>
        </Code>
        <Remarks>
          This example will change the query results link from the file share where the item was crawled to the Web site location from whic
          h the item can be browsed
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlRule </name>
    <synopsis><![CDATA[ Creates a new crawl rule. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlRule cmdlet creates special rules for crawling items that are contained in the specified path For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlRule [-Path] <String> -SearchApplication <SearchServiceApplicationPipeBind> -Type <InclusionRule | ExclusionR
ule> [-AccountName <String>] [-AccountPassword <SecureString>] [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationType <Nu
llable>] [-Confirm [<SwitchParameter>]] [-ContentClass <String>] [-CrawlAsHttp <Nullable>] [-FollowComplexUrls <Nullable>] [-IsAdvancedR
egularExpression <Nullable>] [-PluggableSecurityTimmerId <Nullable>] [-Priority <Nullable>] [-SuppressIndexing <Nullable>] [-WhatIf [<Sw
itchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPEnterpriseSearchCrawlRule -SearchApplication mySearchServiceApp -Identity http://ExampleSharePointSite -CrawlAsHttp 1 -Type 
InclusionRule
]]>
        </Code>
        <Remarks>
          This example creates an inclusion type crawl rule for the site at http://ExampleSharePointSite. The rule specifies that the site
          be crawled as an HTTP site
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchCrawlTopology </name>
    <synopsis><![CDATA[ Adds a crawl topology to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchCrawlTopology cmdlet adds a crawl topology. A crawl topology contains the crawl component collection fo
r a topology on a shared search application. A search service application can contain multiple crawl topologies when a change to a topolo
gy adds or deletes a crawl component For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchCrawlTopology -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection
>] [-Clone <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-CrawlTopology <CrawlTopologyPipeBind>] [-WhatIf [<SwitchParameter>]] [<Co
mmonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$topo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp
New-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -clone -CrawlTopology $topo
]]>
        </Code>
        <Remarks> This example creates a new crawl topology (for adding crawl components) by cloning, or copying, the existing crawl topology </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchLanguageResourcePhrase </name>
    <synopsis><![CDATA[ Adds a language resource phrase to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchLanguageResourcePhrase cmdlet adds a query keyword phrase to a shared search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchLanguageResourcePhrase [-Name] <String> -Language <String> -SearchApplication <SearchServiceApplicationPipeBind> -
Type <Nullable> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Mapping <String>] [-WhatIf [<SwitchPar
ameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
New-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $searchapp -Language en-us -Type QuerySuggestionBlockList -Name secret
]]>
        </Code>
        <Remarks> This example adds a new entry to the QuerySuggestionBlockList for the en-us language </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchMetadataCategory </name>
    <synopsis><![CDATA[ Adds a crawled property category to a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchMetadataCategory cmdlet creates the new crawled property category. SPEnterpriseSearchMetadataCategory r
epresents a category in the enterprise search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchMetadataCategory [-Name] <String> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SP
AssignmentCollection>] [-AutoCreateNewManagedProperties <Nullable>] [-Confirm [<SwitchParameter>]] [-DiscoverNewProperties <Nullable>] [
-MapToContents <Nullable>] [-PropSet <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
New-SPEnterpriseSearchMetadataCategory -SearchApplication $searchapp -Name test -discovernewproperties $True
]]>
        </Code>
        <Remarks> This example shows the creation of a new metadata category </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchMetadataCrawledProperty </name>
    <synopsis><![CDATA[ Adds a crawled property to a search application crawled property category. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchMetadataCrawledProperty cmdlet is used when the search functionality is initially configured, and after
 any new crawled property is added to create the rules for the crawled property. SPEnterpriseSearchMetadataCrawledProperty represents a c
rawled property in the enterprise search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchMetadataCrawledProperty -Category <CategoryPipeBind> -IsNameEnum <$true | $false> -Name <String> -PropSet <Guid> -
SearchApplication <SearchServiceApplicationPipeBind> -VariantType <Int32> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<S
witchParameter>]] [-IsMappedToContents <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$cat = Get-SPEnterpriseSearchMetadataCategory -Identity SharePoint -SearchApplication $searchapp
New-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Category $cat -VariantType 20 -Propset  00000000-0000-1111-
1111-111111111111 -Name testcrawledproperty -IsNameEnum $false
]]>
        </Code>
        <Remarks> This example creates a new crawled property in the SharePoint category (VariantType 20) </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchMetadataManagedProperty </name>
    <synopsis><![CDATA[ Adds a managed property to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchMetadataManagedProperty cmdlet creates a new managed property for a crawled property mapping. SPEnterpr
iseSearchMetadataManagedProperty represents a managed property in the enterprise search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation (http://go.microsoft.com/fwli
nk/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchMetadataManagedProperty [-Name] <String> -SearchApplication <SearchServiceApplicationPipeBind> -Type <Int32> [-Ass
ignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DefaultForQueryIndependentRank <Nullable>] [-Description <S
tring>] [-EnabledForQueryIndependentRank <Nullable>] [-EnabledForScoping <Nullable>] [-FullTextQueriable <Nullable>] [-IncludeInMd5 <Nul
lable>] [-NameNormalized <Nullable>] [-NoWordBreaker <Nullable>] [-RemoveDuplicates <Nullable>] [-RespectPriority <Nullable>] [-Retrieva
ble <Nullable>] [-UserFlags <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
New-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Name testmanagedproperty -Type 1
]]>
        </Code>
        <Remarks> This example adds a new text type managed property to a search application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchMetadataMapping </name>
    <synopsis><![CDATA[ Adds a managed property mapping to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchMetadataMapping cmdlet maps a crawled property and adds the mapping to the managed property. SPEnterpri
seSearchMetadataMapping represents a snapshot of a mapping between a managed property and one or more crawled properties in the enterpris
e search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchMetadataMapping -CrawledProperty <CrawledPropertyPipeBind> -ManagedProperty <ManagedPropertyPipeBind> -SearchAppli
cation <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<Swi
tchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity testmanagedproperty
$prop = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Name testcrawledproperty
New-SPEnterpriseSearchMetadataMapping -SearchApplication $searchapp -CrawledProperty $prop -ManagedProperty $mp
]]>
        </Code>
        <Remarks> This example maps a crawled property to a managed property </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchPropertyDatabase </name>
    <synopsis><![CDATA[ Creates a new property store for use by a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchPropertyDatabase cmdlet creates a new property store for use by a search service application. This cmdl
et is used when the search functionality is initially configured to scale out a search application. The PropertyStore object stores metad
ata about content for a search service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchPropertyDatabase -DatabaseName <String> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollecti
on <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUser
name <String>] [-FailoverDatabaseServer <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp
New-SPEnterpriseSearchPropertyDatabase -SearchApplication $searchApp 
-DatabaseName newPropertyDB
]]>
        </Code>
        <Remarks> This example creates a new property database, newPropertyDB, for the mySearchServiceApp search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchQueryAuthority </name>
    <synopsis><![CDATA[ Adds an authoritative page to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchQueryAuthority cmdlet adds an authoritative page to adjust query rank. SPEnterpriseSearchQueryAuthority
 represents authoritative sites that rank higher in relevance than demoted sites, which are de-emphasized in relevance For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchQueryAuthority [-Url] <String> -Level <Single> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentC
ollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication
New-SPEnterpriseSearchQueryAuthority -SearchApplication $ssa -Url http://contoso.com -Level 1.5
]]>
        </Code>
        <Remarks> This example designates the URL http://contoso.com as an authoritative page with a relative importance of 1.5 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchQueryComponent </name>
    <synopsis><![CDATA[ Adds a query component to a query topology. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchQueryComponent cmdlet is used when the search functionality is initially configured and a new query com
ponent is added to a shared search application. A query topology has one or more index partitions and one or more query components. Query
 components perform user query-generated full-text term search in index partitions For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchQueryComponent -IndexPartition <IndexPartitionPipeBind> -QueryTopology <QueryTopologyPipeBind> -SearchServiceInsta
nce <SearchServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-FailoverOnly <Swit
chParameter>] [-IndexLocation <String>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-ShareName <String>] [-WhatIf [<SwitchP
arameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = GetSPEnterpriseSearchServiceApplication
$qtOld = $ssa | Get-SPEnterpriseSearchQueryTopology -Active
$ssInstance = Get-SPEnterpriseSearchServiceInstance -Local
$qtNew = $ssa | New-SPEnterpriseSearchQueryTopology -Partitions 1 
$idxPartition = (Get-SPEnterpriseSearchIndexPartition -QueryTopology $qtOld)
$queryComponent = New-SPEnterpriseSearchQuerycomponent -QueryTopology $qtNew -IndexPartition $idxPartition -SearchServiceInstance $ssIns
tance
$qtNew | Set-SPEnterpriseSearchQueryTopology -Active
$qtOld | Remove-SPEnterpriseSearchQueryTopology
]]>
        </Code>
        <Remarks>
          This example creates a query topology with a single partition and creates a query component for that topology. It then sets the n
          ewly-created query topology as the active query topology of a search application named MySSA, and deletes the old topology
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchQueryDemoted </name>
    <synopsis><![CDATA[ Adds a demoted site rule to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchQueryDemoted cmdlet adjusts query rank by adding a demoted site rule to the shared search application. 
Query demoted sites are de-emphasized in relevance For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchQueryDemoted [-Url] <String> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssig
nmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceApplication -Identity MySSA | New-SPEnterpriseSearchQueryDemoted -Url http://examplesite
]]>
        </Code>
        <Remarks> This example adds a demoted site rule for the URL http://examplesite.com to a search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchQueryKeyword </name>
    <synopsis><![CDATA[ Adds a keyword term to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchQueryKeyword cmdlet changes query results by creating a new keyword. A query keyword is a query compone
nt of a query topology. SPEnterpriseSearchQueryKeyword represents relevance setting through keywords For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchQueryKeyword [-Term] <String> -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<
SwitchParameter>]] [-Contact <String>] [-Definition <String>] [-EndDate <Nullable>] [-ReviewDate <Nullable>] [-StartDate <Nullable>] [-W
hatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPEnterpriseSearchQueryKeyword -Term Tangible -Site http://myserver/sites/team
]]>
        </Code>
        <Remarks> This example creates a new query keyword for the site http://myserver/sites/team with the term Tangible </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchQueryScope </name>
    <synopsis><![CDATA[ Adds a query results scope to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ Use the New-SPEnterpriseSearchQueryScope cmdlet to create a new shared scope. SPEnterpriseSearchQueryScope represents a query res
ults scope used by all shared search applications on the farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchQueryScope [-Name] <String> -Description <String> -DisplayInAdminUI <Nullable> -SearchApplication <SearchServiceAp
plicationPipeBind> [-AlternateResultsPage <String>] [-AssignmentCollection <SPAssignmentCollection>] [-CompilationType <Nullable>] [-Con
firm [<SwitchParameter>]] [-ExtendedSearchFilter <String>] [-OwningSiteUrl <Uri>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA
$ssa | New-SPEnterpriseSearchQueryScope -Name MustCrawl -Description "Sites we must crawl" -DisplayInAdminUI $true
]]>
        </Code>
        <Remarks>
          This example adds a scope named MustCrawl that will be displayed in the administration UI to the search service application named
          MySSA
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchQueryScopeRule </name>
    <synopsis><![CDATA[ Adds a shared scope rule to a query scope. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchQueryScopeRule cmdlet creates a new shared scope rule. SPEnterpriseSearchQueryScopeRule represents a qu
ery results scope rule that can be applied to a scope For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchQueryScopeRule -RuleType <String> -Scope <ScopePipeBind> -Url <Uri> [-AssignmentCollection <SPAssignmentCollection
>] [-Confirm [<SwitchParameter>]] [-FilterBehavior <String>] [-ManagedProperty <ManagedPropertyPipeBind>] [-MatchingString <String>] [-P
ropertyValue <String>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-UrlScopeRuleType <String>] [-WhatIf [<SwitchParameter>]
] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity

C:\PS>$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa

C:\PS>$sr = New-SPEnterpriseSearchQueryScopeRule -Scope $scope -RuleType AllContent -Url http://criticalSite

C:\PS>Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url http://criticalSite
]]>
        </Code>
        <Remarks> This example creates a new scope rule of type AllContent for the URL http://criticalSite </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchQueryTopology </name>
    <synopsis><![CDATA[ Adds a query topology to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchQueryTopology cmdlet is used when the search functionality is initially configured or when a new query 
topology is created. A search service application can contain multiple query topologies when a query component or index partition is adde
d to or deleted from a topology For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchQueryTopology -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection
>] [-Clone <SwitchParameter>] [-Clone <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-QueryTopology <QueryTopologyPipeBind>] [-WhatI
f [<SwitchParameter>]] [<CommonParameters>]
New-SPEnterpriseSearchQueryTopology -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection
>] [-Clone <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Partitions <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = GetSPEnterpriseSearchServiceApplication
$qtOld = $ssa | Get-SPEnterpriseSearchQueryTopology -Active
$ssInstance = Get-SPEnterpriseSearchServiceInstance -Local
$qtNew = $ssa | New-SPEnterpriseSearchQueryTopology -Partitions 1 
$idxPartition = (Get-SPEnterpriseSearchIndexPartition -QueryTopology $qtOld)
$queryComponent = New-SPEnterpriseSearchQuerycomponent -QueryTopology $qtNew -IndexPartition $idxPartition -SearchServiceInstance $ssIns
tance
$qtNew | Set-SPEnterpriseSearchQueryTopology -Active
$qtOld | Remove-SPEnterpriseSearchQueryTopology
]]>
        </Code>
        <Remarks>
          This example creates a query topology with a single partition and creates a query component for that topology. It sets the new qu
          ery topology as the active query topology of a search service application named MySSA, and deletes the old topology
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchRankingModel </name>
    <synopsis><![CDATA[ Adds a ranking model to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchRankingModel cmdlet adds a new ranking model to the collection. The name, description, and identifier (
ID) for the new ranking model are contained in the .xml file specified in RankingModelXML For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchRankingModel -RankingModelXML <String> -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentCollectio
n <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceApplication -Identity "NewSSA" | New-SPEnterpriseSearchRankingModel -RankingModelXML rankModel.xml
]]>
        </Code>
        <Remarks> This example creates a ranking model for the search service application MySSA from the file rankModel.xml </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchSecurityTrimmer </name>
    <synopsis><![CDATA[ Adds a custom security trimmer to a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchSecurityTrimmer cmdlet creates a new object to configure the pluggable security trimmer. SPEnterpriseSe
archSecurityTrimmer represents a pluggable security trimmer that performs customized security trimming of search results at query time, w
hen the results are returned to the user For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchSecurityTrimmer [-Id] <Int32> -RulePath <String> -SearchApplication <SearchServiceApplicationPipeBind> -TypeName <
String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Properties <String>] [-WhatIf [<SwitchParamete
r>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA"
New-SPEnterpriseSearchSecurityTrimmer -Id 1234 -SearchApplication $ssa -TypeName Contoso.Security.QueryTrimmer -RulePath http://myServer
]]>
        </Code>
        <Remarks> This example adds a new custom security trimmer of type Contoso.Security.QueryTrimmer to the path http://myServer </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Adds a search service application to a farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchServiceApplication cmdlet is used when the search functionality is initially configured or when a new s
hared search application is added to a farm. SPEnterpriseSearchServiceApplication represents a self-contained aggregation of indexed cont
ent and properties available for search, and provides an anchor class for setting global search properties. A farm can include multiple s
earch service applications For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchServiceApplication [[-Name] <String>] -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AdminApplication
Pool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Databas
eName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-FailoverDatabaseServer <Str
ing>] [-Partitioned <SwitchParameter>] [-SearchApplicationType <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$appPool = New-SPIisWebServiceApplicationPool -name "SsaAppPool" -account contoso\adminUser
$ssa =  New-SPEnterpriseSearchServiceApplication -Name "NewSSA" -ApplicationPool $appPool
$searchInstance = Get-SPEnterpriseSearchServiceInstance -Local
$ssa | get-SPEnterpriseSearchAdministrationComponent | set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance $searchInsta
nce
$ssa | Get-SPEnterpriseSearchAdministrationComponent
]]>
        </Code>
        <Remarks>
          This example creates a new search service application named NewSSA in a new application pool and initializes its administration c
          omponent. A search service application created in this way will have active query and crawl topologies, but no query or crawl components.
          } }
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchServiceApplicationProxy </name>
    <synopsis><![CDATA[ Adds a new search application proxy to a farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchServiceApplicationProxy cmdlet creates a proxy for a search service application. The search service app
lication proxy can be used by a Web application or another service consumer to use the functionality provided by the search application.}
 } For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchServiceApplicationProxy [[-Name] <String>] -Uri <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confir
m [<SwitchParameter>]] [-MergeWithDefaultPartition <SwitchParameter>] [-Partitioned <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<C
ommonParameters>]
New-SPEnterpriseSearchServiceApplicationProxy [[-Name] <String>] -SearchApplication <SearchServiceApplicationPipeBind> [-AssignmentColle
ction <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MergeWithDefaultPartition <SwitchParameter>] [-Partitioned <SwitchParam
eter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPEnterpriseSearchServiceApplicationProxy -Name MyNewProxy -SearchApplication MySSA
]]>
        </Code>
        <Remarks> This example adds a search service application proxy to a search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPEnterpriseSearchSiteHitRule </name>
    <synopsis><![CDATA[ Adds a new site hit rule for a search application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPEnterpriseSearchSiteHitRule cmdlet sets the maximum limits for crawling a site. The new site hit rule is used by all se
arch service applications on the current farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPEnterpriseSearchSiteHitRule [-Name] <String> -Behavior <String> -HitRate <String> [-AssignmentCollection <SPAssignmentCollection>]
 [-Confirm [<SwitchParameter>]] [-SearchService <SearchServicePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPEnterpriseSearchSiteHitRule -Identity myHost -Behavior 0 
-HitRate 40
]]>
        </Code>
        <Remarks> This example creates a new site hit rule on the myHost host that limits to 40 the number of simultaneous requests </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPLogFile </name>
    <synopsis><![CDATA[ Creates a new log file. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPLogFile cmdlet ends the current log file and starts a new log file For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPLogFile [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPLogFile
]]>
        </Code>
        <Remarks> This example ends the current log file and starts a new log file </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPManagedAccount </name>
    <synopsis><![CDATA[ Registers a new managed account. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPManagedAccount cmdlet registers a new managed account for the specified Credential or Username, and Password For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPManagedAccount [-Credential] <PSCredential> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-What
If [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$cred = Get-Credential

C:\PS>New-SPManagedAccount -Credential $cred
]]>
        </Code>
        <Remarks> This example adds a new managed account to the farm by using credentials that are prompted </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPManagedPath </name>
    <synopsis><![CDATA[ Creates a new managed path for the given Web application for all host header site collections. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPManagedPath cmdlet adds a new managed path to a given Web application or for use with all host header site collections.
 If the HostHeader switch is provided, the managed path is shared among all host header site collections; otherwise, a Web application mu
st be specified to create this managed path within. The relative URL is a partial URL that represents the managed path. When the slash ma
rk (/) is used, the root is defined. If the Explicit parameter is not provided, the new managed path is a wildcard path For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPManagedPath [-RelativeURL] <String> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-Explicit <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
New-SPManagedPath [-RelativeURL] <String> -HostHeader <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-Explicit <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPManagedPath "Teams" -WebApplication "http://somesite"
]]>
        </Code>
        <Remarks> This example creates a Teams managed path for a given Web application (http://somesite) </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPMetadataServiceApplication </name>
    <synopsis><![CDATA[ Creates a new Metadata Service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the New-SPMetadataServiceApplication cmdlet to create a new service application for the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPMetadataServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> -Name <String> [-AdministratorAccount <String
>] [-AssignmentCollection <SPAssignmentCollection>] [-CacheTimeCheckInterval <Int32>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentia
ls <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-FailoverDatabaseServer <String>] [-FullAccessAccount <String>] 
[-HubUri <String>] [-MaxChannelCache <Int32>] [-PartitionMode <SwitchParameter>] [-RestrictedAccount <String>] [-SyndicationErrorReportE
nabled <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE 1------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPMetadataServiceApplication -Name "MetadataServiceApp1" -ApplicationPool "AppPool1" -DatabaseName "MetadataDB1"
]]>
        </Code>
        <Remarks> This example creates a new Metadata Service application </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 2------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPMetadataServiceApplication -Name "MetadataServiceApp2" -ApplicationPool "AppPool1" -DatabaseName "MetadataDB2" -HubUri "http
://sitename" -SyndicationErrorReportEnabled
]]>
        </Code>
        <Remarks>
          This example creates a new Metadata Service application and specifies a content type hub to be used for syndication. It also enab
          les error reporting during syndication
        </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 3------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPMetadataServiceApplication -Name "MetadataServiceApp3" -ApplicationPool "AppPool1" -DatabaseName "MetadataDB3" -PartitionMod
e
]]>
        </Code>
        <Remarks> This example creates a new Metadata Service application that is partitioned, for use by sites in a subscription </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPMetadataServiceApplicationProxy </name>
    <synopsis><![CDATA[ Creates a new Metadata Service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ Use the New-SPMetadataServiceApplicationProxy cmdlet to create a new service application proxy for the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPMetadataServiceApplicationProxy -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-C
ontentTypePushdownEnabled <SwitchParameter>] [-ContentTypeSyndicationEnabled <SwitchParameter>] [-DefaultKeywordTaxonomy <SwitchParamete
r>] [-DefaultProxyGroup <SwitchParameter>] [-DefaultSiteCollectionTaxonomy <SwitchParameter>] [-PartitionMode <SwitchParameter>] [-Servi
ceApplication <SPMetadataServiceCmdletPipeBind>] [-Uri <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE 1---------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPMetadataServiceApplicationProxy -Name "MetadataServiceProxy1" -ServiceApplication "MetadataServiceApp1"
]]>
        </Code>
        <Remarks>
          This example creates a Metadata Service application proxy connecting to an existing Metadata Service application in the local far
          m
        </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 2---------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPMetadataServiceApplicationProxy -Name "MetadataServiceProxy3" -ServiceApplication "MetadataServiceApp3" -PartitionMode
]]>
        </Code>
        <Remarks>
          This example creates a partitioned Metadata Service application proxy connecting to an existing partitioned Metadata Service appl
          ication in the local farm
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPPerformancePointServiceApplication </name>
    <synopsis><![CDATA[ Creates a new service application for the PerformancePoint Service. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPPerformancePointServiceApplication cmdlet creates a new PerformancePoint Service on the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPPerformancePointServiceApplication [-Name] <String> -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AnalyticQueryCellM
ax <Int32>] [-AnalyticQueryLoggingEnabled <$true | $false>] [-ApplicationCacheEnabled <$true | $false>] [-ApplicationCacheMinimumHitCoun
t <Int32>] [-ApplicationProxyCacheEnabled <$true | $false>] [-AssignmentCollection <SPAssignmentCollection>] [-CommentsDisabled <$true |
 $false>] [-CommentsScorecardMax <Int32>] [-Confirm [<SwitchParameter>]] [-DataSourceQueryTimeoutSeconds <Int32>] [-DecompositionTreeMax
imum <Int32>] [-ElementCacheSeconds <Int32>] [-FilterRememberUserSelectionsDays <Int32>] [-FilterTreeMembersMax <Int32>] [-IndicatorImag
eCacheSeconds <Int32>] [-MSMQEnabled <$true | $false>] [-MSMQName <String>] [-SelectMeasureMaximum <Int32>] [-SessionHistoryHours <Int32
>] [-ShowDetailsInitialRows <Int32>] [-ShowDetailsMaxRows <Int32>] [-ShowDetailsMaxRowsDisabled <$true | $false>] [-TrustedContentLocati
onsRestricted <$true | $false>] [-TrustedDataSourceLocationsRestricted <$true | $false>] [-WhatIf [<SwitchParameter>]] [<CommonParameter
s>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPPerformancePointServiceApplication -Name PPS_Application_01 -ApplicationPool PPS_Application_Pool_01
]]>
        </Code>
        <Remarks>
          This example creates a new PerformancePoint Service application named PPSApp_01 and sets it to run under an application pool name
          d PPS_Application_Pool_01
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPPerformancePointServiceApplicationProxy </name>
    <synopsis><![CDATA[ Creates a proxy for a PerformancePoint Service application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPPerformancePointServiceApplicationProxy cmdlet creates a proxy for a PerformancePoint Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPPerformancePointServiceApplicationProxy [-Name] <String> -ServiceApplication <SPPerformancePointMonitoringServiceApplicationPipeBi
nd> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Default <SwitchParameter>] [-WhatIf [<SwitchParame
ter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPPerformancePointServiceApplicationProxy -Name PPS_Application_Proxy_01 -ServiceApplication PPS_Application_01 -Default
]]>
        </Code>
        <Remarks>
          This example creates a new PerformancePoint Service application proxy named PPS_Application_Proxy_01, associated with the aervice
          application named PPS_Application_01 and is added to the Default proxy group
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPPerformancePointServiceApplicationTrustedLocation </name>
    <synopsis><![CDATA[ Creates a new trusted location for a PerformancePoint Service application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPPerformancePointServiceApplicationTrustedLocation cmdlet creates a new trusted location for a PerformancePoint Service 
application. The new trusted location can be a Content or Data Source trusted location type and is enforced only when it is enabled in th
e PerformancePoint Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPPerformancePointServiceApplicationTrustedLocation -ServiceApplication <SPPerformancePointMonitoringServiceApplicationPipeBind> -Tr
ustedLocationType <DataSource | Content> -Type <SiteCollection | Site | List | DocumentLibrary> -Url <String> [-AssignmentCollection <SP
AssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Description <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPPerformancePointServiceApplicationTrustedLocation -ServiceApplication PPSApp_01 -url "http://Some_Valid_Site_URL" -Type Site
 -TrustedLocationType Content
]]>
        </Code>
        <Remarks>
          This example creates a new TrustedLocation for the PPSApp_01 service application. This creates a Content trusted location of type
          Site with the specified URL
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPProfileServiceApplication </name>
    <synopsis><![CDATA[ Adds a User Profile Service application to a farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPProfileServiceApplication cmdlet adds and creates a new profile service application, or creates an instance of a profil
e service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPProfileServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection
>] [-Confirm [<SwitchParameter>]] [-MySiteHostLocation <SPSitePipeBind>] [-Name <String>] [-PartitionMode <SwitchParameter>] [-ProfileDB
Credentials <PSCredential>] [-ProfileDBFailoverServer <String>] [-ProfileDBName <String>] [-ProfileDBServer <String>] [-ProfileSyncDBCre
dentials <PSCredential>] [-ProfileSyncDBFailoverServer <String>] [-ProfileSyncDBName <String>] [-ProfileSyncDBServer <String>] [-SocialD
BCredentials <PSCredential>] [-SocialDBFailoverServer <String>] [-SocialDBName <String>] [-SocialDBServer <String>] [-SyncInstanceMachin
e <SPServerPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
New-SPProfileServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> -MySiteHostLocation <SPSitePipeBind> [-Assignm
entCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MySiteHostLocation <SPSitePipeBind>] [-MySiteManagedPath <SPPre
fixPipeBind>] [-Name <String>] [-PartitionMode <SwitchParameter>] [-ProfileDBCredentials <PSCredential>] [-ProfileDBFailoverServer <Stri
ng>] [-ProfileDBName <String>] [-ProfileDBServer <String>] [-ProfileSyncDBCredentials <PSCredential>] [-ProfileSyncDBFailoverServer <Str
ing>] [-ProfileSyncDBName <String>] [-ProfileSyncDBServer <String>] [-SiteNamingConflictResolution <String>] [-SocialDBCredentials <PSCr
edential>] [-SocialDBFailoverServer <String>] [-SocialDBName <String>] [-SocialDBServer <String>] [-SyncInstanceMachine <SPServerPipeBin
d>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------EXAMPLE------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$appPool = New-SPIisWebServiceApplicationPool -Name HostedAppPool -Account (Get-SPManagedAccount "contoso\AppPoolAccount")
New-SPProfileServiceApplication -Name PartitionedUserProfileApplication -PartitionMode -ApplicationPool $appPool
]]>
        </Code>
        <Remarks> This example creates a new User Profile Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPProfileServiceApplicationProxy </name>
    <synopsis><![CDATA[ Creates a User Profile Service application proxy on the local farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPProfileServiceApplicationProxy creates a User Profile Service application proxy on the local farm. The proxy is added t
o the default proxy group for the local farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPProfileServiceApplicationProxy -Uri <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Defaul
tProxyGroup <SwitchParameter>] [-Name <String>] [-PartitionMode <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
New-SPProfileServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>]
 [-Confirm [<SwitchParameter>]] [-DefaultProxyGroup <SwitchParameter>] [-Name <String>] [-PartitionMode <SwitchParameter>] [-WhatIf [<Sw
itchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$app = Get-SPServiceApplication -Name PartitionedUserProfileApplication. New-SPProfileServiceApplicationProxy -Name PartitionedUse
rProfileApplication_Proxy -ProfileServiceApplication $app -PartitionMode
]]>
        </Code>
        <Remarks> This example creates a new User Profile Service application proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSecureStoreApplication </name>
    <synopsis><![CDATA[ Creates a new Secure Store application. ]]></synopsis>
    <description><![CDATA[ The New-SPSecureStoreApplication cmdlet creates a new Secure Store application ]]></description>
    <syntax>
      <![CDATA[
New-SPSecureStoreApplication -Fields <TargetApplicationField[]> -ServiceContext <SPServiceContextPipeBind> -TargetApplication <TargetApp
lication> [-Administrator <SPClaim[]>] [-AssignmentCollection <SPAssignmentCollection>] [-CredentialsOwnerGroup <SPClaim[]>] [-TicketRed
eemer <SPClaim[]>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$usernameField = New-SPSecureStoreApplicationField -Name "UserName" -Type WindowsUserName -Masked:$false

$passwordField = New-SPSecureStoreApplicationField -Name "Password" -Type WindowsPassword -Masked:$true

$fields = $usernameField,$passwordField

$userClaim = New-SPClaimsObject -User "CONTOSO\janedoe" -Type WindowsSamAccountName

$contosoTargetApp = New-SPSecureStoreTargetApplication -Name "ContosoTargetApplication" -FriendlyName "Contoso Target Application" -Appl
icationType Group

New-SPSecureStoreApplication -ServiceContext http://contoso -TargetApplication $contosoTargetApp -Fields $fields -Administrator $claimUs
er
]]>
        </Code>
        <Remarks>
          This example creates a new group target application ContosoTargetApplication, and then a new application for that target applicat
          ion. This new application has two fields; UserName of type WindowsUserName, and Password of type WindowsPassword. The user with identity
          janedoe on the CONTOSO domain is set as the target application administrator
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSecureStoreApplicationField </name>
    <synopsis><![CDATA[ Creates a new Secure Store application fields object. ]]></synopsis>
    <description><![CDATA[ The New-SPSecureStoreApplicationField cmdlet creates a new Secure Store application field object for a target application ]]></description>
    <syntax>
      <![CDATA[
New-SPSecureStoreApplicationField -Masked <SwitchParameter> -Name <String> -Type <UserName | Password | Pin | Key | Generic | WindowsUse
rName | WindowsPassword> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSecureStoreApplicationField -Name "UserName" -Type WindowsUserName -Masked:$false
]]>
        </Code>
        <Remarks>
          This example creates a new credential field of type WindowsUserName with the name UserName, and the masked property (which when t
          rue will hide characters as they are typed in by the user) set to false. This cmdlet is typically used in conjunction with the New-SPSecu
          reStoreApplication cmdlet
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSecureStoreServiceApplication </name>
    <synopsis><![CDATA[ Creates a new Secure Store Service application in the farm. ]]></synopsis>
    <description><![CDATA[ The New-SPSecureStoreServiceApplication cmdlet creates a new Secure Store Service application in the farm ]]></description>
    <syntax>
      <![CDATA[
New-SPSecureStoreServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> -AuditingEnabled <SwitchParameter> [-Assig
nmentCollection <SPAssignmentCollection>] [-AuditlogMaxSize <Nullable>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCredenti
al>] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-FailoverDatab
aseServer <String>] [-Name <String>] [-PartitionMode <SwitchParameter>] [-Sharing <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<Com
monParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSecureStoreServiceApplication -ApplicationPool "SharePoint Web Services Default" -AuditingEnabled:$false -DatabaseServer "CO
NTOSO\SharePoint" -DatabaseName "ContosoSSDatabase"-Name "Contoso Secure Store"
]]>
        </Code>
        <Remarks>
          This example creates a new Secure Store Service application with the name Contoso Secure Store with auditing disabled, and create
          s a database with the name ContosoSSDatabase on the given database server for use with the service application
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSecureStoreServiceApplicationProxy </name>
    <synopsis><![CDATA[ Creates a new Secure Store Service application proxy in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPSecureStoreServiceApplicationProxy cmdlet creates a new Secure Store Service application proxy for a Secure Store Servi
ce application in the farm ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPSecureStoreServiceApplicationProxy -Uri <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-De
faultProxyGroup <SwitchParameter>] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
New-SPSecureStoreServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollecti
on>] [-Confirm [<SwitchParameter>]] [-DefaultProxyGroup <SwitchParameter>] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<CommonParame
ters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSecureStoreServiceApplicationProxy -Name "Contoso Service Application Proxy" -ServiceApplication $SSServiceApp
]]>
        </Code>
        <Remarks>
          This example creates a new Secure Store Service application proxy with the name Contoso Service Application Proxy for the given s
          ervice application
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSecureStoreTargetApplication </name>
    <synopsis><![CDATA[ Creates a new Secure Store target application. ]]></synopsis>
    <description><![CDATA[ The New-SPSecureStoreTargetApplication cmdlet creates a new Secure Store Target application ]]></description>
    <syntax>
      <![CDATA[
New-SPSecureStoreTargetApplication -ApplicationType <Individual | Group | IndividualWithTicketing | GroupWithTicketing | RestrictedIndiv
idual | RestrictedGroup> -FriendlyName <String> -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-ContactEmail <String>]
 [-SetCredentialsUri <Uri>] [-TimeoutInMinutes <Int32>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSecureStoreTargetApplication -Name "ContosoTargetApplication" -FriendlyName "Contoso Target Application" -ApplicationType Gr
oup
]]>
        </Code>
        <Remarks> This example creates a new group type target application with the given name and friendly display name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPServiceApplicationPool </name>
    <synopsis><![CDATA[ Creates a new Web service application pool. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPServiceApplicationPool cmdlet creates a new Web service application pool in Internet Information Services (IIS) For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPServiceApplicationPool [-Name] <String> [-Account] <SPProcessAccountPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-C
onfirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPServiceApplicationPool -Name TestServiceWebApplicationPool -Account testdomain\testuser1
]]>
        </Code>
        <Remarks>
          This example creates a new Web service application pool For the Account parameter, the name of a managed account in the farm can be given. Use the Get-SPManagedAccount cmdlet to view th
          e existing managed account in the farm. Also, a process account from the output of the Get-SPProcessAccount cmdlet can be used
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPServiceApplicationProxyGroup </name>
    <synopsis><![CDATA[ Creates a new service application proxy group. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPServiceApplicationProxyGroup cmdlet creates a new service application proxy group specified by the Name parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPServiceApplicationProxyGroup [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Wh
atIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPServiceApplicationProxyGroup -Name RemoteProxyGroup
]]>
        </Code>
        <Remarks> This example creates a new service application proxy with the name RemoteProxyGroup </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSite </name>
    <synopsis><![CDATA[ Creates a new site collection at the specified URL. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPSite cmdlet creates a new site collection with the URL and owner specified by the Url and OwnerAlias parameters For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPSite [-Url] <String> -OwnerAlias <SPUserPipeBind> [-AdministrationSiteType <None | TenantAdministration>] [-AssignmentCollection <
SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-ContentDatabase <SPContentDatabasePipeBind>] [-Description <String>] [-HostHea
derWebApplication <SPWebApplicationPipeBind>] [-Language <UInt32>] [-Name <String>] [-OwnerEmail <String>] [-QuotaTemplate <SPQuotaTempl
atePipeBind>] [-SecondaryEmail <String>] [-SecondaryOwnerAlias <SPUserPipeBind>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-Temp
late <SPWebTemplatePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSite http://sitename/sites/test -OwnerAlias "DOMAIN\JDoe" -Language 1033
]]>
        </Code>
        <Remarks> This example creates an English site collection at http://sitename/sites/test that is owned by user DOMAIN\Jdoe </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$w = Get-SPWebApplication http://sitename

C:\PS>New-SPSite http://www.contoso.com -OwnerAlias "DOMAIN\jdoe" -HostHeaderWebApplication $w -Title "Contoso" -Template "STS#0"
]]>
        </Code>
        <Remarks>
          This example creates a host header site collection. Because the template is provided, the root Web of this site collection will b
          e created
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebTemplate | Where{ $_.Title -eq "Team Site" } | ForEach-Object{ New-SPSite http://sitename/sites/test -OwnerAlias DOMAIN\j
doe -Template $_ }
]]>
        </Code>
        <Remarks> This example creates a site collection by using the "Team Site" Web template </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSiteSubscription </name>
    <synopsis><![CDATA[ Creates a new site subscription. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPSiteSubscription cmdlet creates a new subscription to which the SPSites object can belong.  Sites that are members of a
 site subscription can share settings and configuration information. A site collection can be a member of only one site subscription and,
 once set, cannot be changed Site subscriptions are not persisted in a database until used in conjunction with either an SPSite or the Site Subscription Setti
ngs Service. After a site subscription is applied to any site collection in the farm, the site subscription can be retrieved by using the
 Get-SPSiteSubscription cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPSiteSubscription [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPSiteSubscription |%{ New-SPSite http://contoso.com/sites/admin -SiteSubscription $_ -Template "TenantAdmin#0"}

C:\PS>
]]>
        </Code>
        <Remarks> This example creates a new site subscription and applies it to a new Tenant Administration site collection </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$s = New-SPSiteSubscription

C:\PS>Get-SPSite http://sitename | Set-SPSite -SiteSubscription $s

C:\PS>Set-SPSite http://sitename -SiteSubscription {New-SPSiteSubscription}
]]>
        </Code>
        <Remarks> This example adds a new subscription to an existing site collection at http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSiteSubscriptionFeaturePack </name>
    <synopsis><![CDATA[ Creates a new SharePoint Feature set that can be used to limit the features available to a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ Use the New- SPSiteSubscriptionFeaturePack cmdlet to create a new SharePoint Feature set that limits the Features available to a 
specified site subscription SharePoint Feature sets are on an Allow List of SharePoint Features that can be associated with any site subscription. If a Featu
re set is assigned to a site subscription, only SPFeatures objects in that Feature set are available for use on the site collections and 
Webs that are members of the site subscription. Feature sets contain a list of the GUIDs of each Feature that is on an Allow List for ass
ociated site subscriptions For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPSiteSubscriptionFeaturePack [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParam
eter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$fs = New- SPSiteSubscriptionFeaturePack
]]>
        </Code>
        <Remarks> This example creates a new SharePoint Feature set and stores it in a variable </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPStateServiceApplication </name>
    <synopsis><![CDATA[ Creates a new state service application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPStateServiceApplication cmdlet creates a new state service application on the farm. A state service application is the 
container for state service databases For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPStateServiceApplication [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Database <SPStateDatabasePipeBind>] [<
CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPStateServiceApplication -Name "State Service Application 1"
]]>
        </Code>
        <Remarks>
          This example creates a new state service application, named State Service Application 1, on the farm State service applications are the container for databases. State service applications must have a proxy and a database created t
          o be usable
        </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPStateServiceDatabse -Name "State Service Database" | New-SPStateServiceApplication -Name "StateServiceApp1" | New-SPStateSer
viceApplicationProxy -DefaultProxyGroup
]]>
        </Code>
        <Remarks>
          This example creates a new state service database, a new state service application associated with the database and a new state s
          ervice application proxy associated with the state service application proxy This example configures all the objects required to have State Service operational on a farm
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPStateServiceApplicationProxy </name>
    <synopsis><![CDATA[ Creates a proxy for a state service application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPStateServiceApplicationProxy cmdlet creates a proxy for a state service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPStateServiceApplicationProxy [-ServiceApplication] <SPStateServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollect
ion>] [-DefaultProxyGroup <SwitchParameter>] [-Name <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplication -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b | New-SPStateServiceApplicationProxy -DefaultProxyGroup
]]>
        </Code>
        <Remarks>
          This example creates a new service application proxy, associates it with a provided service application, and adds it to the farm'
          s default proxy group
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Creates and provisions a new state service database, and installs the state database schema into it. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPStateServiceDatabase cmdlet creates and a new state service database. This cmdlet installs the session state database s
chema in the state service database For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPStateServiceDatabase [-Name] <String> [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseCredentials <PSCredential>] [-Dat
abaseServer <String>] [-ServiceApplication <SPStateServiceApplicationPipeBind>] [-Weight <Nullable>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPStateServiceApplication -name "State Service Application 1" | New-SPStateServiceDatabase -Name "statedata1" -DatabaseServer 
"localhost"
]]>
        </Code>
        <Remarks>
          This example creates a new state service database by using Windows authentication, and associates it with the provided service ap
          plication
        </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>$cred = Get-Credential

C:\PS>Get-SPStateServiceApplication -name "State Service Application 1" | New-SPStateServiceDatabase -Name "statedata1" -DatabaseServer 
"localhost" -DatabaseCredentials $cred
]]>
        </Code>
        <Remarks>
          This example creates a new state service database, a new state service application associated with the database and a new state s
          ervice application proxy associated with the state service application proxy This example configures all the objects required to have State Service operational on a farm
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSubscriptionSettingsServiceApplication </name>
    <synopsis><![CDATA[ Creates a new subscription settings service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the New-SPSubscriptionSettingsServiceApplication cmdlet to create a subscription settings service application that can be use
d to store settings that are shared across all site collections in a single site subscription. This cmdlet is used only in an environment
 where site subscriptions are used to delegate administration or partition services that are used for storing settings that are shared ac
ross all site collections in a single site subscription. This cmdlet is used only in an environment where site subscriptions are used to 
delegate administration or partition services For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPSubscriptionSettingsServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignm
entCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>]
 [-FailoverDatabaseServer <String>] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>$AppPool = New-SPIisWebServiceApplicationPool -Name SettingsServiceAppPool -Account (Get-SPManagedAccount DOMAIN\jdoe)

C:\PS>$App = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPool -Name SettingsServiceApp -DatabaseName SettingsServi
ceDB

C:\PS>$proxy = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $App

C:\PS>Get-SPServiceInstance | where{$_.TypeName -eq "Windows SharePoint Services Subscription Settings Service"} | Start-SPServiceInstan
ce
]]>
        </Code>
        <Remarks>
          This example creates an application pool, a new subscription settings service application, a subscription settings service applic
          ation proxy, and starts the service instance on the local machine. This example assumes that a managed account for DOMAIN\jdoe already ex
          ists
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPSubscriptionSettingsServiceApplicationProxy </name>
    <synopsis><![CDATA[ Creates an application proxy to a subscription settings service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the New-SPSubscriptionSettingsServiceApplicationProxy cmdlet to create an application proxy to a subscription settings servic
e application. This is required for the local farm to consume a subscription settings service application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPSubscriptionSettingsServiceApplicationProxy -Uri <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParam
eter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmen
tCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE--------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$AppPool = New-SPIisWebServiceApplicationPool -Name SettingsServiceAppPool -Account (Get-SPManagedAccount DOMAIN\jdoe)

C:\PS>$App = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPool -Name SettingsServiceApp -DatabaseName SettingsServi
ceDB

C:\PS>$proxy = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $App

C:\PS>Get-SPServiceInstance | where{$_.TypeName -eq "Windows SharePoint Services Subscription Settings Service"} | Start-SPServiceInstan
ce
]]>
        </Code>
        <Remarks>
          This example creates an application pool, a new settings service application, a settings service application proxy, and then star
          ts the service instance on the local machine. This example assumes that a managed account for DOMAIN\jdoe already exists
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPTrustedIdentityTokenIssuer </name>
    <synopsis><![CDATA[ Creates an identity provider in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPTrustedIdentityTokenIssuer cmdlet creates an identity provider in the farm. This object is created and used only for se
tting this type of identity provider in a Web application. The specified claim type cannot be NTLM, Classic NTLM, Negotiate, or Classic N
egotiate. For ASP.NET Membership provider or Role providers, no objects are persisted. For security token service (STS) identity provider
s, this cmdlet creates and persists the identity provider object in the SPFarm object For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPTrustedIdentityTokenIssuer -ClaimsMappings <SPClaimMappingPipeBind[]> -Description <String> -IdentifierClaim <String> -Name <Strin
g> -Realm <String> -SignInUrl <String> [-AssignmentCollection <SPAssignmentCollection>] [-ClaimProvider <SPClaimProviderPipeBind>] [-Imp
ortTrustCertificate <X509Certificate2>] [-UseWReply <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------- EXAMPLE--------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPTrustedIdentityTokenIssuer -Name "LiveIDSTS" - Description "LiveID STS" -Certificate (Get-ChildItem"cert:Certificates (Local
Computer)\Personal\Certificates -Name "LiveID Cert") -SignInUrl http://int.contoso.com/ -IdentifierClaim "http://schemas.contoso.com/200
7/05/Claims/Puid"

C:\PS>Set -SPWebApplication http://contoso.com -IdentityProvider (Get-SPTrustedIdentityTokenIssuer "LiveIDSTS")
]]>
        </Code>
        <Remarks> This example creates a new identity provider in the farm named LiveIDSTS </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPTrustedRootAuthority </name>
    <synopsis><![CDATA[ Creates a trusted root authority. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPTrustedRootAuthority cmdlet creates a trusted root authority. If a certificate file is used, it must have only one X509
 certificate without private keys, otherwise an exception is raised For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPTrustedRootAuthority [-Name] <String> -Certificate <X509Certificate2> [-AssignmentCollection <SPAssignmentCollection>] [<CommonPar
ameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx
New - SPTrustedRootAuthority -Name "WFEFarm1" -Certificate $cert
]]>
        </Code>
        <Remarks> This example creates a new trusted root authority, WFEFarm1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPTrustedServiceTokenIssuer </name>
    <synopsis><![CDATA[ Creates a trust with a SharePoint farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPTrustedServiceTokenIssuer cmdlet creates a trust with a SharePoint farm. If a certificate file is used, it must have on
ly one X509 certificate without private keys, otherwise an exception is raised For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPTrustedServiceTokenIssuer [-Name] <String> -Certificate <X509Certificate2> [-AssignmentCollection <SPAssignmentCollection>] [-Desc
ription <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx
New - SPTrustedServiceTokenIssuer -Name "WFEFarm1" - Description "WFE Farm 1" - ImportTrustCertificate $cert
]]>
        </Code>
        <Remarks> This example shows how to create a new SharePoint Farm trust using the trust certificate from a file </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>New - SPTrustedServiceTokenIssuer -Name "WFEFarm1" - Description "WFE Farm 1" -FederationMetadataUrl "https://liveid.com/STS/2007/
03/fedmetadata.xml"
]]>
        </Code>
        <Remarks> This example shows how to create a SharePoint farm trust using the trust certificate from the federation metadata endpoint Url </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPUsageApplication </name>
    <synopsis><![CDATA[ Creates a new usage application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPUsageApplication cmdlet creates a new usage application in the local farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPUsageApplication [[-Name] <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseName
 <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>]
 [-UsageService <SPUsageServicePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPUsageApplication -Name "Usage Application For Farm ABC"
]]>
        </Code>
        <Remarks> This example creates a new usage application for the specified name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPUsageLogFile </name>
    <synopsis><![CDATA[ Starts a new usage log file on the current server computer. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPUsageLogFile cmdlet starts a new usage log file on the current server computer. The usage data in memory is flushed to 
the current usage log file before the new log file is created For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPUsageLogFile [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPUsageLogFile
]]>
        </Code>
        <Remarks> This example terminates the current usage log file and creates a new one </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPUser </name>
    <synopsis><![CDATA[ Adds an existing user to a SharePoint site with the designated permissions. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPUser cmdlet adds an existing user to a SharePoint Web site with the designated permissions.  This user has the given pe
rmissions in all subsites that inherit permissions. The user account must already exist in the user directory If your environment is in Active Directory mode, the user must already exist in Active Directory Domain Services (AD DS) and only
 the UserAlias parameter is required; all other fields are pulled from AD DS. If only an alias is given and the farm is in Active Directo
ry Account Create mode, the Email parameter is also required For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPUser [-UserAlias] <String> -Web <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-
DisplayName <String>] [-Email <String>] [-Group <SPGroupPipeBind>] [-MobileNumber <String>] [-PermissionLevel <String[]>] [-SiteCollecti
onAdmin <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>PS> New-SPUser - UserAlias 'Contoso\Jdoe'-displayname 'John Doe' -web http://contoso.com
]]>
        </Code>
        <Remarks> This example adds a new user named John Doe to the Contoso domain </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWeb http://sitename | New-SPUser -UserAlias Contoso\Jdoe
]]>
        </Code>
        <Remarks>
          This example adds Contoso\Jdoe to all Webs in the http://sitename site collection. Because this site collection uses inherited pe
          rmissions, only the top-level Web site needs to be touched
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPWeb </name>
    <synopsis><![CDATA[ Creates a new site in an existing site collection. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPWeb cmdlet creates a new site in the existing site collection specified by the Url parameter. You can create a site wit
h a specific default language by specifying the Language parameter. If no language is specified, the site is created with the same langua
ge that was specified when the product was installed. You can create a site from a specific template by specifying the Template parameter
. If no template is specified, the site is created and the template can be provided later or by the first user to log on For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPWeb [-Url] <String> [-AddToQuickLaunch <SwitchParameter>] [-AddToTopNav <SwitchParameter>] [-AssignmentCollection <SPAssignmentCol
lection>] [-Confirm [<SwitchParameter>]] [-Description <String>] [-Language <UInt32>] [-Name <String>] [-Template <SPWebTemplatePipeBind
>] [-UniquePermissions <SwitchParameter>] [-UseParentTopNav <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWeb http://somesite/subweb1 -Template "STS#0"
]]>
        </Code>
        <Remarks>
          This example creates a new subsite by using the Team Site template at the provided URL (http://somesite/subweb1). The Team Site t
          emplate is a value referenced as the variable STS#0 for the Template parameter
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPWebAnalyticsServiceApplication </name>
    <synopsis><![CDATA[ Adds a new Web Analytics Service application to the farm. ]]></synopsis>
    <description><![CDATA[ The New-WebAnalyticsServiceApplication cmdlet creates a new Web Analytics Service application in the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http:} } ]]></description>
    <syntax>
      <![CDATA[
New-SPWebAnalyticsServiceApplication -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentColle
ction>] [-Confirm [<SwitchParameter>]] [-EnableDataTrimming <SwitchParameter>] [-ListOfReportingDatabases <String>] [-ListOfStagingDatab
ases <String>] [-MaxAggregationLevel <String>] [-MinAggregationLevel <String>] [-Name <String>] [-ReportingDataRetentionPeriod <Int32>] 
[-SamplingRate <Int32>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWebAnalyticsServiceApplication -Name WebAnalyticsServiceApplication1 -ReportingDataRetention 20 -SamplingRate 100 -Applicati
onPool WebAnalyticsServiceApplication1
]]>
        </Code>
        <Remarks> This example creates a new Web Analytics Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPWebAnalyticsServiceApplicationProxy </name>
    <synopsis><![CDATA[ Adds a new Web Analytics Service application proxy to the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-WebAnalyticsServiceApplicationProxy cmdlet creates a new Web Analytics Service application proxy to the farm or creates a
n instance of a Web Analytics Service application proxy For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http:} } ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPWebAnalyticsServiceApplicationProxy [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Name <String
>] [-ServiceApplication <WebAnalyticsServiceApplicationPipeBind>] [-URI <String>] [-ViewDataPermissionLevel <String>] [-WhatIf [<SwitchP
arameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWebAnalyticsServiceApplicationProxy -Name WebAnalyticsServiceApplicationProxy1 -ServiceApplication WebAnalyticsServiceApplic
ation1
]]>
        </Code>
        <Remarks> This example creates a new Web Analytics Service application proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPWebApplication </name>
    <synopsis><![CDATA[ Creates a new Web application within the local farm. ]]></synopsis>
    <description>
      <![CDATA[ Creates a new Web application specified by the Name parameter. The user specified by the DatabaseCredentials parameter must be a 
member of the dbcreator fixed server role on the database server For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPWebApplication -ApplicationPool <String> -Name <String> [-AdditionalClaimProvider <SPClaimProviderPipeBind[]>] [-AllowAnonymousAcc
ess <SwitchParameter>] [-ApplicationPoolAccount <SPProcessAccountPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Authentic
ationMethod <String>] [-AuthenticationProvider <SPAuthenticationProviderPipeBind[]>] [-Confirm [<SwitchParameter>]] [-DatabaseCredential
s <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-HostHeader <String>] [-Path <String>] [-Port <UInt32>] [-SecureS
ocketsLayer <SwitchParameter>] [-ServiceApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-SignInRedirectProvider <SPTrus
tedIdentityTokenIssuerPipeBind>] [-SignInRedirectURL <String>] [-Url <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>New-SPWebApplication -Name "Contoso Internet Site" -Port 80 -HostHeader "http://sharepoint.contoso.com" -URL "https://www.contoso.
com" -ApplicationPool "ContosoAppPool" -ApplicationPoolAccount (Get-SPManagedAccount "DOMAIN\jdoe")
]]>
        </Code>
        <Remarks>
          This example creates a new Web application by using an internal host header of sharepoint.contoso.com and a public URL of https:/
          /www.contoso.com
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPWebApplicationExtension </name>
    <synopsis><![CDATA[ Creates a new zone instance for the Web application. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPWebApplicationExtension cmdlet creates a new zone instance for the Web application. This is also known as extending a W
eb application and allows alternate permissions to be configured for the same content that is available in the existing Web application.}
 } For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPWebApplicationExtension [-Identity] <SPWebApplicationPipeBind> -Name <String> -Zone <Default | Intranet | Internet | Custom | Extr
anet> [-AdditionalClaimProvider <SPClaimProviderPipeBind[]>] [-AllowAnonymousAccess <SwitchParameter>] [-AssignmentCollection <SPAssignm
entCollection>] [-AuthenticationMethod <String>] [-AuthenticationProvider <SPAuthenticationProviderPipeBind[]>] [-Confirm [<SwitchParame
ter>]] [-HostHeader <String>] [-Path <String>] [-Port <UInt32>] [-SecureSocketsLayer <SwitchParameter>] [-SignInRedirectProvider <SPTrus
tedIdentityTokenIssuerPipeBind>] [-SignInRedirectURL <String>] [-Url <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://sitename | New-SPWebApplicationExtension -Name "ExtranetSite" -SecureSocketsLayer -Zone "Extranet" -UR
L "https://extranet.sitename.com"
]]>
        </Code>
        <Remarks> This example extends the given Web application at http://sitename to the Extranet zone for SSL use </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> New-SPWordConversionServiceApplication </name>
    <synopsis><![CDATA[ Creates a new instance of a Word Automation Services application on the farm. ]]></synopsis>
    <description>
      <![CDATA[ The New-SPWordConversionServiceApplication cmdlet creates a new instance of a Word Automation Services application on the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
New-SPWordConversionServiceApplication -Name <String> -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <
SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseCredential <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <
String>] [-Default <SwitchParameter>] [-PartitionMode <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplicationPool -Identity MyAppPool | New-SPWordConversionServiceApplication -Name WordServices1
]]>
        </Code>
        <Remarks>
          This example creates a new Word Automation Services application named WordServices1 in an existing application pool named MyAppPo
          ol
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Ping-SPEnterpriseSearchContentService </name>
    <synopsis><![CDATA[ Sends a request to the content distributor. ]]></synopsis>
    <description>
      <![CDATA[ Use the Ping-SPEnterpriseSearchContentService cmdlet to send a request to the content distributor to determine whether the conten
t distributor is available For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Ping-SPEnterpriseSearchContentService [-HostName] <String> [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Ping-SPEnterpriseSearchContentService -HostName "FASTServer1.mydomain.com"
]]>
        </Code>
        <Remarks> This example sends a request to a content distributor on the host with the name FASTServer1.mydomain.com </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Publish-SPServiceApplication </name>
    <synopsis><![CDATA[ Shares the specified local service application outside the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Publish-SPServiceApplication cmdlet publishes the local service application, specified by the Identity parameter, outside the
 farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Publish-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-Description <String>] [-InfoLink <Uri>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Publish-SPServiceApplication 053c34be-d251-488c-8e94-644eae94da26 -Description "Connect to this TestServiceApplcation of you want 
to use FeatureA in your farm" -InfoLink http://testurl
]]>
        </Code>
        <Remarks>
          This example publishes a service application to another farm The service application GUID is unique to every farm. You can run the Get-SPServiceApplication cmdlet to see the GUID of the serv
          ice applications, and then use the result from the Get-SPServiceApplication cmdlet for other SPServiceApplication cmdlets; for example, G
          rant-SPServiceApplication
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Receive-SPServiceApplicationConnectionInfo </name>
    <synopsis><![CDATA[ Configures this farm to receive service information from another farm. ]]></synopsis>
    <description>
      <![CDATA[ The Receive-SPServiceApplicationConnectionInfo cmdlet retrieves the list of service applications published by another farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Receive-SPServiceApplicationConnectionInfo [-FarmUrl] <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Filter <String>] [<Common
Parameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Receive-SPServiceApplicationConnectionInfo -FarmUrl http://FarmB/topology/topology.svc
]]>
        </Code>
        <Remarks> This example retreives a list of service applications published by a given farm The FarmURL parameter can be obtained by the Get-SPTopologyServiceApplication cmdlet </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPAlternateURL </name>
    <synopsis><![CDATA[ Completely deletes the specified alternate URL. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPAlternateUrl cmdlet completely deletes the alternate URL specified by the Identity parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPAlternateUrl [-Identity] <SPAlternateUrlPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>
]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPAlternateURL -WebApplication http://sitename -Zone Extranet
]]>
        </Code>
        <Remarks> This example deletes the extranet URL for the given Web application </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication |%{ Get-SPAlternateURL -WebApplication $_ -Zone "Extranet" } | Remove-SPAlternateURL
]]>
        </Code>
        <Remarks> This example removes all extranet alternate URLs in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPBusinessDataCatalogModel </name>
    <synopsis><![CDATA[ Deletes a Business Data Connectivity Model. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPBusinessDataCatalogModel cmdlet deletes a Business Data Connectivity Model For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPBusinessDataCatalogModel -Identity <MetadataObject> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParamete
r>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$modelFile = Get-SPBusinessDataCatalogMetadataObject -Name "ContosoModel" -BdcObjectType Model -ServiceContext http://contoso
Remove-SPBusinessDataCatalogModel -Identity $modelFile
]]>
        </Code>
        <Remarks> This example removes the Business Data Connectivity Model file named ContosoModel </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPClaimProvider </name>
    <synopsis><![CDATA[ Unregisters a claim provider. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPClaimProvider cmdlet unregisters a claim provider. If the unregistered claim provider was assigned to a trusted iden
tity token issuer, the trusted token issuer will use the default (system) claim provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPClaimProvider [-Identity] <SPClaimProviderPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove - SPClaimProvider -Identity "12345678-90ab-cdef-1234-567890bcdefgh"
]]>
        </Code>
        <Remarks> This example removes a claim provider from the farm} } </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPClaimTypeMapping </name>
    <synopsis><![CDATA[ Deletes a claim type mapping rule for a security token service (STS) identity provider. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPClaimMapping cmdlet deletes a claim type mapping rule from a farm trust STS identity provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPClaimTypeMapping [-Identity] <SPClaimMappingPipeBind> [-TrustedIdentityTokenIssuer] <SPTrustedIdentityTokenIssuerPipeBind> [-As
signmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPClaimMapping "Email" | Get-SPIdentityProvider "LiveIDSTS"
]]>
        </Code>
        <Remarks> This example removes an identity provider named LiveIDSTS </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPConfigurationDatabase </name>
    <synopsis><![CDATA[ Permanently removes a configuration database. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPConfigurationDatabase cmdlet permanently removes the farm's configuration database. The configuration database must 
be already dismounted from any associated farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPConfigurationDatabase [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParamete
r>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPConfigurationDatabase
]]>
        </Code>
        <Remarks> This example permanently deletes a configuration database from a farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPContentDatabase </name>
    <synopsis><![CDATA[ Deletes a content database. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPContentDatabase cmdlet deletes a content database permanently from Microsoft SQL Server 2008 R2, SQL Server 2008 wit
h Service Pack 1 (SP1), or SQL Server 2005 with SP3. In situations where data needs to be persisted, use the Dismount-SPContentDatabase c
mdlet. This will remove the content database from SharePoint 2010 Products but not from SQL Server 2008 R2, SQL Server 2008 with SP1, or 
SQL Server 2005 with SP3 For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPara
meter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDatabase 12345678-90ab-cdef-1234-567890abcdef | Remove-SPContentDatabase
]]>
        </Code>
        <Remarks> This example deletes the specified content database </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPContentDeploymentJob </name>
    <synopsis><![CDATA[ Removes a content deployment job. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPContentDeploymentJob cmdlet removes a content deployment job For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPContentDeploymentJob -Identity <SPContentDeploymentJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Sw
itchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPContentDeploymentJob -Identity "DeployJob1"
]]>
        </Code>
        <Remarks> This example removes a deployment job named DeployJob1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPContentDeploymentPath </name>
    <synopsis><![CDATA[ Removes a content deployment path. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPContentDeploymentPath cmdlet removes a content deployment path For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPContentDeploymentPath -Identity <SPContentDeploymentPathPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<
SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPContentDeploymentPath -Path1
]]>
        </Code>
        <Remarks> This example removes a content path named Path1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPDiagnosticsPerformanceCounter </name>
    <synopsis><![CDATA[ Removes an instance of a performance counter. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPDiagnosticsPerformanceCounter cmdlet removes performance counters from the collection of performance counters that a
re read and recorded in the Usage Database. This cmdlet can also be used to remove entire categories and types of counters from the colle
ction as well. If either the DatabaseServer or WebFrontEnd parameters are not specified, this cmdlet removes the specified performance co
unters on the Web front end computers in the farm The Remove-SPDiagnosticsPerformanceCounter cmdlet is only available using Windows PowerShell. There is no User Interface For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPDiagnosticsPerformanceCounter [-Category] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter
>]] [-Counter <String>] [-DatabaseServer <SwitchParameter>] [-Instance <String>] [-WebFrontEnd <SwitchParameter>] [-WhatIf [<SwitchParam
eter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPDiagnosticsPerformanceCounter -category ASP.NET
]]>
        </Code>
        <Remarks> This example removes all the counters in the category ASP.NET on Web front end computers </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPDiagnosticsPerformanceCounter -category ASP.NET -Counter "Requests Queued"
]]>
        </Code>
        <Remarks> This example removes the counters in the category ASP.NET that have requests queued on Web front end computers </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPDiagnosticsPerformanceCounter -category Processor -counter "% Processor Time" -instance "_Total" -databaseserver
]]>
        </Code>
        <Remarks>
          This example removes the counters of the _Total instance, with the counter % Processor Time in the category Processor on database
          servers
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlComponent </name>
    <synopsis><![CDATA[ Deletes a crawl component from a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchCrawlComponentAdmin cmdlet deletes a specified crawl component from a shared service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlComponent [-Identity] <CrawlComponentPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm 
[<SwitchParameter>]] [-CrawlTopology <CrawlTopologyPipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchP
arameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1)"
$topo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp
New-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -clone -CrawlTopology $topo
$newtopo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -Identity 11111111-1111-1111-1111-111111111111
$cc = Get-SPEnterpriseSearchCrawlComponent -CrawlTopology $newtopo -Identity 22222222-2222-2222-2222-222222222222
$cc | Remove-SPEnterpriseSearchCrawlComponent
$newtopo | Set-SPEnterpriseSearchCrawlTopology -Active
]]>
        </Code>
        <Remarks>
          This example creates a new, inactive crawl topology, removes a crawl component from the crawl topology, and then activates the ne
          w crawl topology
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlContentSource </name>
    <synopsis><![CDATA[ Deletes a specified crawl content source from a search application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchCrawlContentSource cmdlet deletes a specified crawl content source from a service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confi
rm [<SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$topo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp
New-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -clone -CrawlTopology $topo
$newtopo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -Identity 11111111-1111-1111-1111-111111111111
$cc = Get-SPEnterpriseSearchCrawlComponent -CrawlTopology $newtopo -Identity 22222222-2222-2222-2222-222222222222
$cc | Remove-SPEnterpriseSearchCrawlComponent
$newtopo | Set-SPEnterpriseSearchCrawlTopology -Active
]]>
        </Code>
        <Remarks> This example creates a new, inactive, crawl topology, removes a crawl component from it, and activates the new crawl topology </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlCustomConnector </name>
    <synopsis><![CDATA[ Removes a CustomConnector object. ]]></synopsis>
    <description>
      <![CDATA[ The Get-SPEnterpriseSearchCrawlCustomConnector selects the custom connector or connectors, and then pipes them to the Remove-SPEn
terpriseSearchCrawlCustomConnector cmdlet For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlCustomConnector -Identity <SPCustomConnectorPipeBind> -SearchApplication <SearchServiceApplicationPipeBind
> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchCrawlCustomConnector -SearchApplication MySearchServiceApp" - Identity "dctm://" | Remove-SPEnterpriseSearch
CrawlCustomConnector
]]>
        </Code>
        <Remarks> This example removes a custom connector for the dctm://  protocol from the MySearchServiceApp search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlDatabase </name>
    <synopsis><![CDATA[ Deletes a crawl database. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchCrawlDatabase cmdlet deletes a specified crawl database from a search service application. A crawl d
atabase stores crawl history for a search service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlDatabase [-Identity] <CrawlStorePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPEnterpriseSearchCrawlDatabase -Identity CrawlDB-0
-SearchApplication mySearchServiceApp
]]>
        </Code>
        <Remarks> This example removes the CrawlDB-0 crawl database from the mySearchServiceApp search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlExtension </name>
    <synopsis><![CDATA[ Removes a file name extension from the list of files that can be crawled. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchCrawlExtension cmdlet prevents files with this extension from being crawled For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlExtension [-Identity] <ExtensionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> Add code example. </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$searchapp | Get-SPEnterpriseSearchCrawlExtension "pdf" | Remove-SPEnterpriseSearchCrawlExtension
]]>
        </Code>
        <Remarks>
          This example removes the PDF IFilter and removes the pdf file extension from the list of file types to include in the content ind
          ex
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlMapping </name>
    <synopsis><![CDATA[ Deletes a crawl mapping. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchCrawlMapping cmdlet deletes a crawl mapping from the crawl mapping collection For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlMapping [-Identity] <CrawlMappingPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Sw
itchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "Sample Search Service Application"
$mappingtodelete = Get-SPEnterpriseSearchCrawlContentSource -Identity "somemapping"
$mappingtodelete | Remove-SPEnterpriseSearchCrawlMapping
]]>
        </Code>
        <Remarks> This example removes a crawl mapping from a search application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlRule </name>
    <synopsis><![CDATA[ Deletes a crawl rule. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchCrawlRule cmdlet deletes a crawl rule that is used to crawl content for a content source For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlRule [-Identity] <CrawlRulePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp
Remove-SPEnterpriseSearchCrawlRule -Identity http://mySPSite 
-SearchApplication $searchApp
]]>
        </Code>
        <Remarks> This example removes a crawl rule pertaining to the path http://mySPSite from the mySearchServiceApp search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchCrawlTopology </name>
    <synopsis><![CDATA[ Deletes a crawl topology. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchCrawlTopology cmdlet deletes a specified crawl topology from the crawl topology collection. A crawl 
topology contains the crawl component collection for a topology on a shared search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchCrawlTopology [-Identity] <CrawlTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<
SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$topo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -Identity FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF
$topo | Remove-SPEnterpriseSearchCrawlTopology
]]>
        </Code>
        <Remarks> This example retrieves the inactive crawl topology and removes it </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchLanguageResourcePhrase </name>
    <synopsis><![CDATA[ Deletes a language resource phrase from a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchLanguageResourcePhrase cmdlet deletes one or more language resource phrases from the collection of l
anguage resource phrases in a shared search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchLanguageResourcePhrase [-Identity] <LanguageResourcePhrasePipeBind> -Language <String> -SearchApplication <Sear
chServiceApplicationPipeBind> -Type <Nullable> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Mapping
 <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$obsoletephrase = Get-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $searchapp -Language en-us -Type QuerySuggestionBlockL
ist -Identity secret
$obsoletephrase | Remove-SPEnterpriseSearchLanguageResourcePhrase -SearchApplication $searchapp -Type QuerySuggestionBlockList -Language
 en-us
]]>
        </Code>
        <Remarks> This example removes a language resource item on the QuerySuggestionBlockList for the en-us language </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchMetadataCategory </name>
    <synopsis><![CDATA[ Deletes a crawled property category. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchMetadataCategory cmdlet deletes a crawled property category. Use this cmdlet after a crawl to delete
 unused or unwanted categories from the metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchMetadataCategory [-Identity] <CategoryPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Sw
itchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$cat = Get-SPEnterpriseSearchMetadataCategory -Identity test2 -SearchApplication $searchapp
$cat | Remove-SPEnterpriseSearchMetadataCategory
]]>
        </Code>
        <Remarks> This example shows the removal of a metadata category named test2 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchMetadataManagedProperty </name>
    <synopsis><![CDATA[ Deletes a metadata managed property. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchManagedProperty cmdlet deletes unused or unwanted managed properties from the managed property colle
ction For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchMetadataManagedProperty [-Identity] <ManagedPropertyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] 
[-Confirm [<SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>
]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity testmanagedproperty
$mp | Remove-SPEnterpriseSearchMetadataManagedProperty
]]>
        </Code>
        <Remarks> This example removes the managed property testmanagedproperty from the search service application, SearchApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchMetadataMapping </name>
    <synopsis><![CDATA[ Deletes a metadata mapping from a managed property. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchMetadataMapping cmdlet deletes unused or unwanted mappings from a managed property. A metadata mappi
ng is the mapping between a managed property and one or more crawled properties in the enterprise search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchMetadataMapping [-Identity] <MappingPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swit
chParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity testmanagedproperty
$prop = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Name testcrawledproperty
$map = Get-SPEnterpriseSearchMetadataMapping -SearchApplication $searchapp -CrawledProperty $prop -ManagedProperty $mp
$map | Remove-SPEnterpriseSearchMetadataMapping
]]>
        </Code>
        <Remarks>
          This example removes the metadata mapping between the crawled property testcrawledproperty and the managed property testmanagedpr
          operty
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchPropertyDatabase </name>
    <synopsis><![CDATA[ Deletes a property store. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchPropertyDatabase cmdlet deletes a specified property store from the property store collection. A pro
perty store stores metadata about content for a search service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchPropertyDatabase [-Identity] <PropertyStorePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm
 [<SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPEnterpriseSearchPropertyDatabase -Identity PropertyDB
-SearchApplication mySearchServiceApp
]]>
        </Code>
        <Remarks> This example removes the property database, PropertyDB, from the mySearchServiceApp search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchQueryAuthority </name>
    <synopsis><![CDATA[ Deletes an authoritative page. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchQueryAuthority cmdlet adjusts query rank by deleting an authoritative page. SPEnterpriseSearchQueryA
uthority represents authoritative sites that rank higher in relevance than demoted sites, which are de-emphasized in relevance For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchQueryAuthority [-Identity] <AuthorityPagePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [
<SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPEnterpriseSearchQueryAuthority -Identity http://contoso.com -SearchApplication MySSA
]]>
        </Code>
        <Remarks> This example removes the query authority URL http://contoso.com from the search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchQueryComponent </name>
    <synopsis><![CDATA[ Deletes a query component. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchQueryComponent cmdlet deletes a query component from the query component collection For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) } } ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchQueryComponent [-Identity] <QueryComponentPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm 
[<SwitchParameter>]] [-QueryTopology <QueryTopologyPipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchP
arameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterproseSearchServiceApplication -Identity MySSA
Remove-SPEnterpriseSearchQueryComponent -Identity ($ssa | Get-SPEnterpriseSearchQueryTopology -Active | Get-SPEnterpriseSearchQueryCompo
nent)
]]>
        </Code>
        <Remarks> This example removes the query component from the active query topology of a search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchQueryDemoted </name>
    <synopsis><![CDATA[ Deletes a demoted site rule. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchQueryDemoted cmdlet adjusts query rank by deleting a demoted site rule from the demoted site collect
ion. Query demoted sites are de-emphasized in relevance For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchQueryDemoted [-Identity] <DemotedPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchP
arameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$demotedRule = Get-SPEnterpriseSearchQueryDemoted -Identity http://somesite.com -SearchApplication MySSA
$demotedRule | Remove-SPEnterpriseSearchQueryDemoted
]]>
        </Code>
        <Remarks> This example obtains a reference to a site demotion rule for the URL http://somesite.com, and removes it </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchQueryKeyword </name>
    <synopsis><![CDATA[ Deletes a query keyword. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchQueryKeyword cmdlet deletes unused or unwanted keywords from the query keyword collection For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchQueryKeyword [-Identity] <KeywordPipeBind> -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollectio
n>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchQueryKeyword -Identity Engineering -Site http://myserver/sites/engineering | Remove-SPEnterpriseSearchQueryK
eyword -Site http://myserver/sites/engineering
]]>
        </Code>
        <Remarks> This example removes the Engineering keyword from the site collection at http://myserver/sites/engineering </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchQueryScope </name>
    <synopsis><![CDATA[ Deletes a query scope. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchQueryScope cmdlet deletes one or more specified shared scopes from the query scope collection. A que
ry scope represents a query results scope used by all shared search applications on the farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchQueryScope [-Identity] <ScopePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParam
eter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-Url <Uri>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPenterpriseSearchServiceApplication -Identity MySSA
Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa | Remove-SPEnterpriseSearchQueryScope
]]>
        </Code>
        <Remarks> This example removes a scope named MustCrawl from a search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchQueryScopeRule </name>
    <synopsis><![CDATA[ Deletes query results scope rules. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchQueryScopeRule cmdlet deletes one or more shared scope rules from the scope rule collection For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchQueryScopeRule [-Identity] <ScopeRulePipeBind> -Url <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Co
nfirm [<SwitchParameter>]] [-Scope <ScopePipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]
] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA"
$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa
Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url http://criticalSite | Remove-SPEnterpriseSearchQueryScopeRule -Url http://critic
alSite
]]>
        </Code>
        <Remarks> This example removes a scope rule for the URL http://criticalSite from a search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchQueryTopology </name>
    <synopsis><![CDATA[ Deletes a query topology. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchQueryTopology cmdlet deletes a specified query topology from the query topology collection For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchQueryTopology [-Identity] <QueryTopologyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<
SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA
$qtList = $ssa | Get-SPEnterpriseSearchQueryTopology
$qtList
Id              : 668b6492-c8b5-4272-82e5-34c6eeddd215
IndexPartitions : {2785d65d-4e2d-4d8d-b374-fb6fcca08c4d}
QueryComponents : {b189cb8c-fe61-4984-8378-0449b5e4c2ba-query-0}
State           : Active
ActivationError :

Id              : 3884c529-5ef2-4182-81cb-5a28e70312b5
IndexPartitions : {20620966-0a3b-4348-abca-a762d0b9876c}
QueryComponents : {b189cb8c-fe61-4984-8378-0449b5e4c2ba-query-0}
State           : Inactive
ActivationError :

$qtList[1] | Remove-SPEnterpriseSearchQueryTopology
]]>
        </Code>
        <Remarks>
          This example obtains the collection of query topologies of a search service application named MySSA, and removes the inactive top
          ology
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchRankingModel </name>
    <synopsis><![CDATA[ Deletes a ranking model. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchRankingModel cmdlet deletes a specified ranking model For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchRankingModel [-Identity] <RankingModelPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Sw
itchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$rankingModel = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA" | Get-SPEnterpriseSearchRankingModel
$rankingModel[0] |  Remove-SPEnterpriseSearchRankingModel
]]>
        </Code>
        <Remarks> This example removes the first ranking model of the collection of ranking models for the search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchSecurityTrimmer </name>
    <synopsis><![CDATA[ Deletes a custom security trimmer. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchSecurityTrimmer cmdlet deletes the customized security trimmer that is used for a search application
's query results. A custom security trimmer trims search results before the results are returned to the user For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchSecurityTrimmer [-Identity] <SecurityTrimmerPipeBind> -SearchApplication <SearchServiceApplicationPipeBind> [-A
ssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchSecurityTrimmer -SearchApplication MySSA |  Remove-SPEnterpriseSearchSecurityTrimmer
]]>
        </Code>
        <Remarks> This example removes the pluggable security trimmer registered in the search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Deletes a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchServiceApplication cmdlet deletes a specified search service application from a farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollectio
n>] [-Confirm [<SwitchParameter>]] [-RemoveData <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPEnterpriseSearchServiceApplication -Identity MySSA
]]>
        </Code>
        <Remarks> This example removes the search service application named MySSA from the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchServiceApplicationProxy </name>
    <synopsis><![CDATA[ Deletes a search service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchServiceApplicationProxy cmdlet deletes the specified search service application proxy from a farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchServiceApplicationProxy [-Identity] <SearchServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmen
tCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPEnterpriseSearchServiceApplicationProxy -Identity SearchProxy
]]>
        </Code>
        <Remarks> This example removes a search service application proxy named SearchProxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPEnterpriseSearchSiteHitRule </name>
    <synopsis><![CDATA[ Deletes a site hit rule. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPEnterpriseSearchSiteHitRule cmdlet deletes the site hit rule that controls the number of threads used to crawl a giv
en site For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPEnterpriseSearchSiteHitRule [-Identity] <SiteHitRulePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swit
chParameter>]] [-SearchService <SearchServicePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>
Remove-SPEnterpriseSearchSiteHitRule -Identity myHost
]]>
        </Code>
        <Remarks> This example removes a site hit rule for the myHost host </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPInfoPathUserAgent </name>
    <synopsis><![CDATA[ Removes a user agent. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPIPUserAgent cmdlet removes a specified user agent from the user agent collection on a farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPInfoPathUserAgent -Identity <SPUserAgentPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>
]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPInfoPathUserAgent -Identity "UserAgentName"
]]>
        </Code>
        <Remarks> This example removes a user agent </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPManagedAccount </name>
    <synopsis><![CDATA[ Removes a managed account registration from the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPManagedAccount cmdlet removes account registration from the configuration database within the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParame
ter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Remove-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -NewPassword <SecureString> [-AssignmentCollection <SPAssignmentCollectio
n>] [-ChangePassword <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPManagedAccount -Identity DOMAIN\ServiceAcct
]]>
        </Code>
        <Remarks> This example removes the DOMAIN\ServiceAcct managed account from the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPManagedPath </name>
    <synopsis><![CDATA[ Deletes the specified managed path from the specified host header or Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPManagedPath cmdlet deletes the managed path specified by the Identity parameter from the host header or the Web appl
ication. The Identity must be the partial URL of the managed path to be deleted If you are using host headers, specify the HostHeader parameter. To delete a HostHeader managed path, provide the HostHeader swit
ch.  Otherwise, you must specify the Web Application that contains the managed path to be deleted For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPManagedPath [-Identity] <SPPrefixPipeBind> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentColle
ction>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Remove-SPManagedPath [-Identity] <SPPrefixPipeBind> -HostHeader <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-Con
firm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------EXAMPLE 1---------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPManagedPath "sites" -HostHeader
]]>
        </Code>
        <Remarks> This example removes the sites managed path from the list of HostHeader managed paths Depending on the confirmation level of the local system, the preceding example can prompt prior to execution </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication | Remove-SPManagedPath "personal" -confirm:$false
]]>
        </Code>
        <Remarks>
          This example removes the personal managed path from all Web applications in the farm. This command does not prompt for confirmati
          on
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPPerformancePointServiceApplication </name>
    <synopsis><![CDATA[ Deletes a PerformancePoint Service application from a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPPerformancePointServiceApplication cmdlet deletes a PerformancePoint Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPPerformancePointServiceApplication [-Identity] <SPPerformancePointMonitoringServiceApplicationPipeBind> [-AssignmentCollection 
<SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPPerformancePointServiceApplication -Identity PPSApp_01
]]>
        </Code>
        <Remarks> This example removes the PPSApp_01 PerformancePoint Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPPerformancePointServiceApplicationProxy </name>
    <synopsis><![CDATA[ Deletes the proxy for a PerformancePoint Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPPerformancePointServiceApplicationProxy cmdlet deletes the proxy for a PerformancePoint Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPPerformancePointServiceApplicationProxy [-Identity] <SPPerformancePointMonitoringServiceApplicationProxyPipeBind> [-AssignmentC
ollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPPerformancePointServiceApplicationProxy -Identity PPS_Application_Proxy_01
]]>
        </Code>
        <Remarks> This example removes the PPS_Application_Proxy_01 application proxy from its associated PerformancePoint Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPPerformancePointServiceApplicationTrustedLocation </name>
    <synopsis><![CDATA[ Removes a single trusted location from a PerformancePoint Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPPerformancePointServiceApplicationTrustedLocation cmdlet deletes a single trusted location from a PerformancePoint S
ervice application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPPerformancePointServiceApplicationTrustedLocation -Identity <SPPerformancePointMonitoringServiceApplicationTrustedLocationPipeB
ind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPPerformancePointServiceApplicationTrustedLocation -Identity <Valid GUID of one a Trusted Location in an Application>
]]>
        </Code>
        <Remarks> This example removes a Trusted Location having the specified GUID from a PerformancePoint Service Application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPPluggableSecurityTrimmer </name>
    <synopsis>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Remove-SPPluggableSecurityTrimmer [-UserProfileApplicationProxyId] <Guid> -PlugInId <Int32> [-AssignmentCollection <SPAssignmentCollecti
on>] [-Verbose] [-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariab
le <String>] [-OutVariable <String>] [-OutBuffer <Int32>] [-WhatIf] [-Confirm]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSecureStoreApplication </name>
    <synopsis><![CDATA[ Deletes a Secure Store application. ]]></synopsis>
    <description><![CDATA[ The Remove-SPSecureStoreApplication cmdlet deletes a Secure Store application ]]></description>
    <syntax>
      <![CDATA[
Remove-SPSecureStoreApplication -Identity <SPSecureStoreApplication> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switch
Parameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApp" | Remove -SPSecureStoreApplication
]]>
        </Code>
        <Remarks> This example removes the specified application and target </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPServiceApplication </name>
    <synopsis><![CDATA[ Deletes the specified service application on the local server. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPServiceApplication cmdlet deletes the specified service application from the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swit
chParameter>]] [-RemoveData <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE--------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPServiceApplication 053c34be-d251-488c-8e94-644eae94da26 
-removedata
]]>
        </Code>
        <Remarks>
          This example deletes the service application and its database The service application GUID is unique to every farm. You can run the Get-SPServiceApplication cmdlet to see the GUID of the serv
          ice applications, and then use the result from the Get-SPServiceApplication cmdlet for other SPServiceApplication cmdlets; for example, G
          rant-SPServiceApplication or Publish-SPServiceApplication
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPServiceApplicationPool </name>
    <synopsis><![CDATA[ Completely deletes the specified Web service application pool. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPServiceApplicationPool cmdlet completely deletes the specified Web service application pool For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPServiceApplicationPool [-Identity] <SPIisWebServiceApplicationPoolPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPServiceApplicationPool TestServiceWebApplicationPool
]]>
        </Code>
        <Remarks> This example deletes the selected service application pool </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPServiceApplicationProxy </name>
    <synopsis><![CDATA[ Deletes the specified service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPServiceApplicationProxy cmdlet deletes the service application proxy specified by the Identity parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPServiceApplicationProxy [-Identity] <SPServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Conf
irm [<SwitchParameter>]] [-RemoveData <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPServiceApplicationProxy babab30e-8e3a-428b-8ff4-4d5c8f455e6d
]]>
        </Code>
        <Remarks>
          This example deletes the given service application proxy The service application GUID is unique to every farm. You can run the Get-SPServiceApplication cmdlet to see the GUID of the serv
          ice applications, and then use the result from the Get-SPServiceApplication cmdlet for other SPServiceApplication cmdlets; for example, G
          rant-SPServiceApplication or Publish-SPServiceApplication
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPServiceApplicationProxyGroup </name>
    <synopsis><![CDATA[ Completely deletes the specified service application proxy group. ]]></synopsis>
    <description>
      <![CDATA[ Completely deletes the specified service application proxy group For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPServiceApplicationProxyGroup [-Identity] <SPServiceApplicationProxyGroupPipeBind> [-AssignmentCollection <SPAssignmentCollectio
n>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPServiceApplicationProxyGroup RemoteProxyGroup
]]>
        </Code>
        <Remarks>
          This example deletes the service application proxy group named RemoteProxyGroup The service application proxy group GUID is unique to every farm. You can run Get-SPServiceApplicationProxyGroup | Select Name,Id
          to see the GUID of the service application proxy groups. Use this result for any other SPServiceApplicationProxyGroup cmdlets
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPServiceApplicationProxyGroupMember </name>
    <synopsis><![CDATA[ Removes one or more proxies from the specified service application proxy group. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPServiceApplicationProxyGroupMember cmdlet removes one or more proxies from the specified service application proxy g
roup For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPServiceApplicationProxyGroupMember [-Identity] <SPServiceApplicationProxyGroupPipeBind> [-Member] <SPServiceApplicationProxyPip
eBind[]> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameter
s>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPServiceApplicationProxyGroupMember RemoteProxyGroup -Member babab30e-8e3a-428b-8ff4-4d5c8f455e6d
]]>
        </Code>
        <Remarks>
          This example removes a service application proxy from the selected service application proxy group named RemoteProxyGroup The service application proxy group GUID is unique to every farm. You can run Get-SPServiceApplicationProxyGroup | Select Name,Id
          to see the GUID of the service application proxy groups. Use this result for any other SPServiceApplicationProxyGroup cmdlets
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPShellAdmin </name>
    <synopsis><![CDATA[ Removes a user from the SharePoint_Shell_Access role. ]]></synopsis>
    <description>
      <![CDATA[ Use the Remove-SPShellAdmin cmdlet to remove a user from the SharePoint_Shell_Access role in a specified database When you use this cmdlet to remove a user from the role, you do not remove the user from the WSS_ADMIN_WPG group in the target da
tabase When you run this cmdlet to add a user to the SharePoint_Shell_Access role, the user must have the following security permissions
:} } - Security_Admin role access on the SQL instance and the db_owner role in the database - Administrative permission to the local computer For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPShellAdmin [-UserName] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-database <SPD
atabasePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------------EXAMPLE----------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPShellAdmin -UserName CONTOSO\User1 -database WSS_Content
]]>
        </Code>
        <Remarks> This example removes an existing user named User1 from the SharePoint_Shell_Access role in the WSS_Content database </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSite </name>
    <synopsis><![CDATA[ Completely deletes an existing site collection and all subsites. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPSite cmdlet completely deletes an existing site collection and all subsites. This operation cannot be undone For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSite [-Identity] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DeleteADAcc
ounts <SwitchParameter>] [-GradualDelete <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSite -Identity "http://sitename" -GradualDelete -Confirm:$False
]]>
        </Code>
        <Remarks> This example removes the given site collection and all included sites by using GradualDelete; confirmation has been suppressed </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSiteSubscription </name>
    <synopsis><![CDATA[ Removes data stored in a subscription settings service application for a set of site subscriptions. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPSiteSubscription cmdlet removes a site subscription along with all contained site collections and settings For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSiteSubscription [-Identity] <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSiteSubscription "http://contoso.com"
]]>
        </Code>
        <Remarks> This example removes all data for the contoso.com site subscription (site collections, site subscription, and settings) </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSiteSubscriptionBusinessDataCatalogConfig </name>
    <synopsis><![CDATA[ Removes the Business Data Connectivity Metadata Store for a partition. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPBusinessDataCatalogSiteSubscriptionConfig cmdlet removes the Business Data Connectivity Metadata Store and all assoc
iated data for a specified partition. To completely remove a partition and the data that it contains, run the Clear-SPSiteSubscriptionBus
inessDataCatalogConfig cmdlet to remove the data from the Business Data Connectivity Metadata Store, and then run the Remove-SPBusinessDa
taCatalogSiteSubscriptionConfig cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSiteSubscriptionBusinessDataCatalogConfig -ServiceContext <SPServiceContextPipeBind> [-AssignmentCollection <SPAssignmentCollec
tion>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPBusinessDataCatalogSiteSubscriptionConfig -ServiceContext http://contoso
]]>
        </Code>
        <Remarks> This example removes the Business Data Connectivity Metadata Store for the partition http://contoso </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSiteSubscriptionFeaturePack </name>
    <synopsis><![CDATA[ Removes a SharePoint Feature set from a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ The Remove- SPSiteSubscriptionFeaturePack cmdlet removes a SharePoint Feature set by specifying the GUID or Feature set object For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSiteSubscriptionFeaturePack [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> [-AssignmentCollection <SPAssignmentCollection>
] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPFeatureSet -Identity "30daa535-b0fe-4d10-84b0-fb04029d161a"
]]>
        </Code>
        <Remarks> This example removes a SharePoint Feature set that has the ID 30daa535-b0fe-4d10-84b0-fb04029d161a </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSiteSubscriptionFeaturePackMember </name>
    <synopsis><![CDATA[ Removes a feature definition from the provided SharePoint Feature set. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPSiteSubscriptionFeaturePackMember cmdlet removes the provided FeatureDefintion parameter from the feature set specif
ied by the Identity parameter. If the AllFeatureDefinitions flag is provided, all feature definitions are removed from the given Feature 
set For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSiteSubscriptionFeaturePackMember [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> -FeatureDefinition <SPFeatureDefinitionPi
peBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters
>]
Remove-SPSiteSubscriptionFeaturePackMember [-Identity] <SPSiteSubscriptionFeaturePackPipeBind> -AllFeatureDefinitions <SwitchParameter> 
[-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$FS = Get-SPSiteSubscriptionFeaturePack "30daa535-b0fe-4d10-84b0-fb04029d161a"

C:\PS>Remove-SPSiteSubscriptionFeaturePackMember -Identity $fs -FeatureDefinition (Get-SPFeature "PublishingSite")
]]>
        </Code>
        <Remarks> This example removes the PublishingSite feature from the Feature set that has ID 30daa535-b0fe-4d10-84b0-fb04029d161a </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteSubscriptionFeaturePack "30daa535-b0fe-4d10-84b0-fb04029d161a" | Remove-SPSiteSubscriptionFeaturePackMember -AllFeatureD
efinitions
]]>
        </Code>
        <Remarks> This example removes all features from the Feature set 30daa535-b0fe-4d10-84b0-fb04029d161a </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSiteSubscriptionMetadataConfig </name>
    <synopsis><![CDATA[ Removes site subscription configuration settings. ]]></synopsis>
    <description>
      <![CDATA[ Use the Remove-SPSiteSubscriptionMetadataConfig cmdlet to remove the site subscription-specific configuration settings for a spec
ified Metadata Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSiteSubscriptionMetadataConfig -Identity <SPSiteSubscriptionPipeBind> -ServiceProxy <SPMetadataServiceProxyCmdletPipeBind> [-As
signmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSiteSubscriptionMetadataConfig -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2"
]]>
        </Code>
        <Remarks> This example removes the site subscription-specific settings from an existing partitioned Metadata Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSiteSubscriptionProfileConfig </name>
    <synopsis><![CDATA[ Deletes a site subscription from a User Profile Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPSiteSubscriptionProfileConfig cmdlet deletes a site subscription from a User Profile Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> -ProfileServiceApplicationProxy <SPServiceApplicationPro
xyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParame
ters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>$sub = Get-SPSiteSubscription http://contoso/my

C:\PS>$pr = Get-SPServiceApplicationProxy | ? {$_.DisplayName.Contains(PartitionedUserProfileApplication_Proxy)}Remove-SPSiteSubscriptio
nProfileConfig -Identity $sub -ProfileServiceApplicationProxy $pr
]]>
        </Code>
        <Remarks> This example removes tenant data </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSiteSubscriptionSettings </name>
    <synopsis><![CDATA[ Removes the settings service data for a specified site subscription, or finds and removes orphaned data. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPSiteSubscriptionSettings cmdlet deletes site subscription stored data for the specified site subscription. If the Fi
ndAllOrphans parameter is specified, this cmdlet locates any data in the service application that does not exist in the list of local sit
e subscriptions or the alternate list of subscriptions The set of site subscriptions can be specified directly, or discovered by comparing data in the service application to the set of
 existing site subscriptions which finds the data set that corresponds to nonexistent site subscriptions If this cmdlet is run on a federated service application without specifying the complete list of site subscription IDs for the Al
ternativeSiteSubscriptions parameter, data loss can result For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSiteSubscriptionSettings [-Identity] <SPServiceApplicationPipeBind> -SiteSubscriptions <Guid[]> [-AssignmentCollection <SPAssig
nmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Remove-SPSiteSubscriptionSettings [-Identity] <SPServiceApplicationPipeBind> -FindAllOrphans <SwitchParameter> [-AlternativeSiteSubscrip
tions <Guid[]>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-WhatIf [<Sw
itchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------EXAMPLE 1-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSiteSubscriptionSettings -FindAllOrphans -Whatif
]]>
        </Code>
        <Remarks> This example finds all orphans and displays them on the screen. Remove the WhatIf parameter to remove these extra settings </Remarks>
      </example>
      <example>
        <title> ------------EXAMPLE 2-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSubscriptionSettingsServiceApplication -FindAllOrphans -AlternativeSiteSubscriptions $SubscriptionList
]]>
        </Code>
        <Remarks>
          Use this example if the service application is consumed by a remote farm and you want the clean orphaned site subscription settin
          gs data (an array of all site subscriptions whose data must remain in the service application is assigned to the $SubscriptionList variab
          le
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSocialItemByDate </name>
    <synopsis><![CDATA[ Deletes tags, notes, or ratings. ]]></synopsis>
    <description>
      <![CDATA[ Use the Remove-SPSocialItemByDate cmdlet to delete, tags, notes, ratings created before a particular date For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSocialItemByDate -EndDate <DateTime> -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-AssignmentCollection
 <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-RemoveComments <$true | $false>] [-RemoveRatings <$true | $false>] [-RemoveT
ags <$true | $false>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSocialItemByDate -RemoveTags 1 -ProfileServiceApplicationProxy c6681d53-e6c4-432f-9f31-22d3de81b00c -EndDate 9/15/2009
]]>
        </Code>
        <Remarks> This example removes tags before 9/15/09 from the specified User Profile Service Application Proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSolution </name>
    <synopsis><![CDATA[ Removes a SharePoint solution from a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPSolution cmdlet deletes a SharePoint solution from a farm. Before you use this cmdlet, you must use the Uninstall-SP
Solution cmdlet to retract the solution files from the front-end Web server For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSolution [-Identity] <SPSolutionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-For
ce <SwitchParameter>] [-Language <UInt32>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSolution -Identity contoso_solution.wsp
]]>
        </Code>
        <Remarks> This example removes the SharePoint solution contoso_solution.wsp </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPSolutionDeploymentLock </name>
    <synopsis><![CDATA[ Removes the solution deployment lock for a server. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPSolutionDeploymentLock cmdlet removes the solution deployment lock for a server. If the Identity parameter is not sp
ecified, this cmdlet removes the solution deployment lock for all servers in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPSolutionDeploymentLock [[-Identity] <SPServerPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPara
meter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPSolutionDeploymentLock
]]>
        </Code>
        <Remarks> This example removes the solution deployment lock for all servers in the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Removes a state service database from a state service application and drops it from the SQL Server. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPStateServiceDatabase cmdlet removes a state service database from a state service application and deletes the databa
se. To remove a state service database and not delete the database, use the Dismount-SPStateServiceDatabase cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchP
arameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b
]]>
        </Code>
        <Remarks>
          This example removes the specified database from a Microsoft SharePoint Server 2010 farm and drops the database from the SQL Serv
          er (data loss)
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPTrustedIdentityTokenIssuer </name>
    <synopsis><![CDATA[ Deletes a security token service (STS) identity provider from the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPTrustedIdentityTokenIssuer cmdlet deletes a security token service (STS) identity provider from the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPTrustedIdentityTokenIssuer [-Identity] <SPTrustedIdentityTokenIssuerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] 
[-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------------------EXAMPLE---------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPTrustedIdentityTokenIssuer "LiveIDSTS"
]]>
        </Code>
        <Remarks> This example removes an identity provider named LiveIDSTS from the farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPTrustedRootAuthority </name>
    <synopsis><![CDATA[ Deletes a trusted root authority. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPTrustedRootAuthority cmdlet deletes a trusted root authority from a signing certificate store For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPTrustedRootAuthority [-Identity] <SPTrustedRootAuthorityPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<
SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove - SPTrustedRootAuthority -Name "WFEFarm1"
]]>
        </Code>
        <Remarks> This example removes the trusted root authority WFEFarm1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPTrustedServiceTokenIssuer </name>
    <synopsis><![CDATA[ Deletes the object that represents the farm trust. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPTrustedServiceTokenIssuer cmdlet deletes the object that represents the farm trust For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPTrustedServiceTokenIssuer [-Identity] <SPTrustedServiceTokenIssuerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Remove - SPTrustedServiceTokenIssuer "WFE Farm 2"
]]>
        </Code>
        <Remarks> This example deletes the trusted service token issuer WFE Farm 2 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPUsageApplication </name>
    <synopsis><![CDATA[ Removes a usage application from the local farm. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPUsageApplication cmdlet deletes a usage application from the local farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPUsageApplication [-Identity] <SPUsageApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-RemoveData <SwitchParameter>] [-UsageService <SPUsageServicePipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPUsageApplication -Identity "Usage and Health data collection" -RemoveData
]]>
        </Code>
        <Remarks> This example removes the existing usage application and the associated logging DB </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPUser </name>
    <synopsis><![CDATA[ Removes a user from a Web site. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPUser cmdlet specifies the identity and user group from which a user is to be removed. The Remove-SPUser cmdlet does 
not remove the user from Active Directory Domain Services (AD DS) For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPUser [-Identity] <SPUserPipeBind> -Web <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParam
eter>]] [-Group <SPGroupPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPUser "Contoso \jdoe" -web http://test/web1

C:\PS>Get-SPWeb "http://test/web1" | Remove-SPUser "Contoso\jdoe"
]]>
        </Code>
        <Remarks> This example removes the user (Contoso\jdoe) from the Web application http://test/web1 </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite http://contoso.com |Get-SPWeb |Remove-SPUser "Contoso\jdoe"
]]>
        </Code>
        <Remarks> This syntax removes the user (Contoso\Jdoe) from every Web in a site collection located at http://contoso.com </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPUserSolution </name>
    <synopsis><![CDATA[ Removes a sandboxed solution from the solution gallery. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPUserSolution cmdlet completely removes a sandboxed solution from the solution gallery. Before you can remove the san
dboxed solution from the solution gallery, you must deactivate it by using the Uninstall-SPUserSolution cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPUserSolution [-Identity] <String> -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPar
ameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPUserSolution -Identity contoso_solution.wsp -Site http://sitename
]]>
        </Code>
        <Remarks> This example removes the sandboxed solution contoso_solution.wsp from the site http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPWeb </name>
    <synopsis><![CDATA[ Completely deletes the specified Web. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPWeb cmdlet completely deletes the Web specified by the Identity parameter Deleting the top level Web site of a site collection causes the entire site collection to be removed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPWeb [-Identity] <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<Swit
chParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPWeb http://sitename/subsite
]]>
        </Code>
        <Remarks> This example completely deletes a subsite </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPWebApplication </name>
    <synopsis><![CDATA[ Deletes the specified Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPWebApplication cmdlet deletes the Web application specified by the Identity and Zone parameters. If no zone is provi
ded, the entire Web application and all zones are removed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPWebApplication [-Identity] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParame
ter>]] [-DeleteIISSite <SwitchParameter>] [-RemoveContentDatabases <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Remove-SPWebApplication [-Identity] <SPWebApplicationPipeBind> -Zone <Default | Intranet | Internet | Custom | Extranet> [-AssignmentCol
lection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DeleteIISSite <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://sitename | Remove-SPWebApplication -Zone "Internet" -Confirm
]]>
        </Code>
        <Remarks>
          This example prompts and then removes the Internet zone Web application extension on the Web application at http://sitename. This
          command does not remove the content databases or the IIS Web site
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Remove-SPWebApplication http://sitename -Confirm -DeleteIISSite -RemoveContentDatabases
]]>
        </Code>
        <Remarks> This example permanently removes the Web application, all content databases, and the IIS Web site at http://sitename} } </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Remove-SPWordConversionServiceJobHistory </name>
    <synopsis><![CDATA[ Removes entries from the Word Automation Services job history database. ]]></synopsis>
    <description>
      <![CDATA[ The Remove-SPWordConversionServiceJobHistory cmdlet removes entries from the Word Automation Services job history database For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Remove-SPWordConversionServiceJobHistory -Identity <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Bef
oreDate <Nullable>] [-Confirm [<SwitchParameter>]] [-IncludeActiveJobs <SwitchParameter>] [-JobId <Nullable>] [-SubscriptionId <Nullable
>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE 1------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplication -Name TestWordServer | Remove-SPWordConversionServiceJobHistory -BeforeDate 1/1/2009
]]>
        </Code>
        <Remarks> This example deletes all the items in the database before 1/1/2009 </Remarks>
      </example>
      <example>
        <title> ---------------------EXAMPLE 2------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplication -Name TestWordServer | Remove-SPWordConversionServiceJobHistory -JobId 00000000-0000-0112-08FF-63927635FE
F1 -IncludeActiveJobs
]]>
        </Code>
        <Remarks> This example deletes the job with the specified ID, even if it is still processing </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Rename-SPServer </name>
    <synopsis><![CDATA[ Renames a server that is currently connected to the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Rename-SPServer cmdlet changes the name of the server for internal use within SharePoint 2010 Products. The server itself mus
t be manually renamed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Rename-SPServer [-Identity] <SPServerPipeBind> -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParamet
er>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Rename-SPServer -Identity "wfb1" -Name "WFE1"
]]>
        </Code>
        <Remarks> This example changes the name of the SharePoint server wfb1 to WFE1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Repair-SPManagedAccountDeployment </name>
    <synopsis><![CDATA[ Repairs the local managed account credential deployment. ]]></synopsis>
    <description>
      <![CDATA[ Use the Repair-SPManagedAccountDeployment cmdlet to repair the local deployment of managed account credentials deployment on a se
rver for the rare cases that the managed accounts service credentials are in a broken state. It re-deploys each local service and Web app
lications credentials and also determines if the passphrase is not correct on the server and repairs provides warnings accordingly. The R
epair-SPManagedAccountDeployment cmdlet should not be used as part of the regular credential update process, but should be one of the fir
st troubleshooting steps, specifically if a servers' services are failing to start when other servers' services are working correctly For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Repair-SPManagedAccountDeployment [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParam
eter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------EXAMPLE----------- </title>
        <Code>
          <![CDATA[
C:\PS>Repair-SPManagedAccountDeployment
]]>
        </Code>
        <Remarks>
          This example repairs the deployment of credentials on all services and Web application associated with managed account (s) on the
          local server
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Restart-SPEnterpriseSearchQueryComponent </name>
    <synopsis><![CDATA[ Restarts a failed query component. ]]></synopsis>
    <description>
      <![CDATA[ The Restart-SPEnterpriseSearchQueryComponent cmdlet recovers a failed query component from its redundant component under the same
 index partition. There must be redundant query components (at least two) serving one index partition, one of which being in Ready state.
} } If this query component is offline because of some failures --for example, index corruption, low disk, or out-of- sync -- a user 
can recover this component by running this cmdlet Although the Restart-SPEnterpriseSearchQueryComponent cmdlet is designed to recover a failed (offline) query component, it can al
so be called on a Ready component to clone one that has the same index files as its source component For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Restart-SPEnterpriseSearchQueryComponent [-Identity] <QueryComponentPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm
 [<SwitchParameter>]] [-QueryTopology <QueryTopologyPipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<Switch
Parameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = GetSPEnterpriseSearchServiceApplication -Identity MySSA
$qt = $ssa.QueryTopologies
$qc = Get-SPEnterpriseSearchQueryComponent -QueryTopology $qt.ActiveTopology
$qc | fl Name,State

Name  : 06f80fa2-c043-41cf-9b73-1c86037be74e-query-1
State : Ready

Name  : 06f80fa2-c043-41cf-9b73-1c86037be74e-query-0
State : Offline

$qc[0] |  Restart-SPEnterpriseSearchQueryComponent
]]>
        </Code>
        <Remarks> This example restarts a query component in the active query topology of a search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Restore-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Restores third-party backup of a search application. ]]></synopsis>
    <description>
      <![CDATA[ The Restore-SPEnterpriseSearchServiceApplication cmdlet is used by third parties to create a search application that uses existin
g data Some third parties back up the application data and need to restore the application later. So the data is restored and uses the R
estore-SPEnterpriseSearchServiceApplication cmdlet to create a new search application that uses the restored data This cmdlet supports parameter sets. The first set of parameters is for Application Configuration Attach mode and the second set 
of parameters is for Search Application Attach mode Application Configuration Attach mode only restores configuration data that is stored in the administration database. However, Se
arch Application Attach restores configuration, topology and all crawled data For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Restore-SPEnterpriseSearchServiceApplication [-Name] <String> -AdminSearchServiceInstance <SearchServiceInstancePipeBind> -ApplicationPo
ol <SPIisWebServiceApplicationPoolPipeBind> -DatabaseName <String> -DatabaseServer <String> [-AdminApplicationPool <SPIisWebServiceAppli
cationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabasePassword <SecureString>] 
[-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Restore-SPEnterpriseSearchServiceApplication [-Name] <String> -ApplicationPool <SPIisWebServiceApplicationPoolPipeBind> -TopologyFile <S
tring> [-AdminApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-KeepId <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------EXAMPLE 1-------------- </title>
        <Code>
          <![CDATA[
C:\PS>$searchInstance = Get-SPEnterpriseSearchServiceInstance -local
$applicationPool = New-SPIisWebServiceApplicationPool -Name "SearchServiceApplicationPool"

C:\PS>Restore-SPEnterpriseSearchServiceApplication -Name "SearchServiceApplication" -ApplicationPool $applicationPool -AdminSearchServic
eInstance $searchInstance -DatabaseName "SearchServiceApplication_Admindb" -DatabaseServer "SQLServer1"
]]>
        </Code>
        <Remarks> This example uses Application Configuration Attach mode to restore configuration data </Remarks>
      </example>
      <example>
        <title> -------------EXAMPLE 2-------------- </title>
        <Code>
          <![CDATA[
C:\PS>$applicationPool = New-SPIisWebServiceApplicationPool -Name "SearchServiceApplicationPool"

C:\PS>Restore-SPEnterpriseSearchServiceApplication -Name "SearchServiceApplication" -ApplicationPool $applicationPool -TopologyFile "C:\
TopologyFile.xml"
]]>
        </Code>
        <Remarks> This example uses Search Application Attach mode to restore toplogoy data in the file named topology.xml </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Restore-SPFarm </name>
    <synopsis><![CDATA[ Restores one or more items from a backup. ]]></synopsis>
    <description>
      <![CDATA[ The Restore-SPFarm cmdlet restores one or more items from a backup such as an individual database, Web application, or the entire
 farm. This cmdlet can also be used to apply a farm template to the entire farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Restore-SPFarm -Directory <String> -RestoreMethod <String> [-AssignmentCollection <SPAssignmentCollection>] [-BackupId <Guid>] [-Configu
rationOnly <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-FarmCredentials <PSCredential>] [-Force <SwitchParameter>] [-Item <String
>] [-NewDatabaseServer <String>] [-Percentage <Int32>] [-RestoreThreads <Int32>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Restore-SPFarm -Directory <String> -ShowTree <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-BackupId <Guid>] [-Con
figurationOnly <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Item <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Restore-SPFarm -Directory \\file_server\share\Backup -BackupId 12345678-90ab-cdef-1234-567890abcdef -RestoreMethod new -Configurat
ionOnly
]]>
        </Code>
        <Remarks>
          This example restores the configuration settings from the backup package in the \\file_server\share\Backup directory to the farm.
          } }
        </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Restore-SPFarm -ShowTree -Directory \\file_server\share\Backup -BackupId 12345678-90ab-cdef-1234-567890abcdef -Item "Microsoft Sha
rePoint Foundation Web Application" -Verbose
]]>
        </Code>
        <Remarks>
          This example show which components of the farm would be restored under the Microsoft SharePoint Foundation Web Application node,
          but does not actually restore them
        </Remarks>
      </example>
      <example>
        <title> -------------------EXAMPLE 3----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Restore-SPFarm -Directory C:\Backup -BackupId 12345678-90ab-cdef-1234-567890abcdef  -RestoreMethod overwrite -RestoreThreads 10 -F
orce
]]>
        </Code>
        <Remarks> This example restores a farm by using 10 threads and suppresses the overwrite warning </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Restore-SPSite </name>
    <synopsis><![CDATA[ Restores a site collection. ]]></synopsis>
    <description>
      <![CDATA[ The Restore-SPSite cmdlet performs a restoration of the site collection to a location specified by the Identity parameter. A cont
ent database may only contain one copy of a site collection. If a site collection is backed up and restored to a different URL location w
ithin the same Web application, an additional content database must be available to hold the restored copy of the site collection For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Restore-SPSite [-Identity] <String> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Con
tentDatabase <SPContentDatabasePipeBind>] [-Force <SwitchParameter>] [-GradualDelete <SwitchParameter>] [-HostHeaderWebApplication <Stri
ng>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Restore-SPSite [-Identity] <String> -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Dat
abaseName <String>] [-DatabaseServer <String>] [-Force <SwitchParameter>] [-GradualDelete <SwitchParameter>] [-HostHeaderWebApplication 
<String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------EXAMPLE 1---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Restore-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak
]]>
        </Code>
        <Remarks>
          This example restores a site collection from the backup file C:\Backup\site_name.bak to the site collection URL http://server_nam
          e/sites/site_name
        </Remarks>
      </example>
      <example>
        <title> ----------------------EXAMPLE 2---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Restore-SPSite http://server_name/sites/site_name -Path C:\Backup\site_name.bak -Force -DatabaseServer SQLBE1 -DatabaseName SQLDB1
]]>
        </Code>
        <Remarks>
          This example restores a site collection backup from the backup file C:\Backup\site_name.bak, but overwrites the existing site col
          lection at http://server_name/sites/site_name while specifying that the site collection must be stored in a specific content database
        </Remarks>
      </example>
      <example>
        <title> ----------------------EXAMPLE 3---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Restore-SPSite http://www.example.com -Path \\file_server\share\site_name.bak -HostHeaderWebApplication http://server_name
]]>
        </Code>
        <Remarks>
          This example restores a site collection backup from the backup file \\file_server\share\site_name.bak to the host-named site coll
          ection http://www.example.com on the Web application http://server_name
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Resume-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Resumes a search service application that was suspended. ]]></synopsis>
    <description>
      <![CDATA[ The Resume-SPEnterpriseSearchServiceApplication cmdlet reads the SearchServiceApplication object and moves it from the Paused for
: External Request state to the Online state. If the Identity parameter is not specified, all search service applications from the farm a
re returned as a collection For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Resume-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollectio
n>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA
$ssa | Resume-SPEnterpriseSearchServiceApplication
]]>
        </Code>
        <Remarks> This example obtains a reference to a search service application named MySSA and then resumes it </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Resume-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Resumes a paused state service database so that new rows of data are received. ]]></synopsis>
    <description>
      <![CDATA[ The Resume-SPStateServiceDatabase cmdlet resumes a paused state service database, an operation that adds the state service databa
se to the set of databases that can receive new data as required by Microsoft SharePoint Server 2010 applications For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Resume-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchP
arameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Resume-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b
]]>
        </Code>
        <Remarks> This example resumes a paused state service database </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Revoke-SPBusinessDataCatalogMetadataObject </name>
    <synopsis><![CDATA[ Revokes a right to a principal in the specified Business Data Connectivity Metadata Store metadata object. ]]></synopsis>
    <description>
      <![CDATA[ The Revoke-SPBusinessDataCatalogMetadataObject cmdlet revokes a right granted to a principal user in the specified Business Data 
Connectivity Metadata Store metadata object For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Revoke-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> -Principal <SPClaim> -Right <Execute | Edit | SetPermissions | Sel
ectableInClients> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-SettingId <String>] [-WhatIf [<Switc
hParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$claimJohn = New-SPClaimObject -User "CONTOSO\johndoe" -Type windowssamaccountname
$MetadataObject = Get-SPBusinessDataCatalogMetadataObject -BdcObjectType "LobSystem" -ServiceContext http://contoso -Name "ContosoDataba
se"
Revoke-SPBusinessDataCatalogMetadataObject -Identity $MetadataObject -Principal $claimJohn -Right "Execute"
]]>
        </Code>
        <Remarks>
          This example removes the execute right from the External System with the name ContosoDatabase for the user with the identity of j
          ohndoe on the domain CONTOSO
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Revoke-SPObjectSecurity </name>
    <synopsis><![CDATA[ Removes a security principal from a SPObjectSecurity object. ]]></synopsis>
    <description>
      <![CDATA[ The Revoke-SPObjectSecurity cmdlet to remove a security principal, such as a user, from a SPObjectSecurity object. An SPObjectSec
urity object is a common object that is used to represent the security access control list (ACL) of SharePoint administrative objects, in
 particular service applications For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Revoke-SPObjectSecurity [-Identity] <SPObjectSecurity> [-Principal] <SPClaim> [[-Rights] <String[]>] [-AssignmentCollection <SPAssignmen
tCollection>] [<CommonParameters>]
Revoke-SPObjectSecurity [-Identity] <SPObjectSecurity> -All <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [<CommonP
arameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$security = Get-SPServiceApplicationSecurity $serviceApp -Admin
Revoke-SPObjectSecurity $security "domain\user"
Set-SPServiceApplicationSecurity $serviceApp -Admin $security
]]>
        </Code>
        <Remarks>
          This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on a service application, and removes a
          user from that ACL. The removed an administrator for the service application $serviceApp
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPAlternateURL </name>
    <synopsis><![CDATA[ Configures the specified alternate URL. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPAlternateUrl cmdlet changes the URL or zone of the alternate URL specified by the Identity parameter. This cmdlet can b
e used to change only the zone of internal URLs, and cannot be used to change the zone of public URLs For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPAlternateUrl [-Identity] <SPAlternateUrlPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] 
[-Url <String>] [-WhatIf [<SwitchParameter>]] [-Zone <Default | Intranet | Internet | Custom | Extranet>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPAlternateURL -Identity https://www.contoso.com -Zone "Internet"
]]>
        </Code>
        <Remarks> This example changes the zone of the alternate URL https://www.contoso.com </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPAlternateURL -Identity https://www.contoso.com -Url https://sharepoint.contoso.com -Zone "Default"
]]>
        </Code>
        <Remarks> This example changes the URL and zone of the alternate URL https://www.contoso.com </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPAlternateURL https://www.contoso.com | Set-SPAlternateURL -Zone "Internet"
]]>
        </Code>
        <Remarks> This example changes the zone of the alternate URL https://www.contoso.com </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 4------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication |%{ Get-SPAlternateURL -WebApplication $_ -Zone "Extranet" } | Set-SPAlternateURL -Zone "Intranet"
]]>
        </Code>
        <Remarks> This example changes the zone of the alternate URL for the specified Web application from Extranet to Intranet </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPBrowserCustomerExperienceImprovementProgram </name>
    <synopsis><![CDATA[ Turns on or off the browser Customer Experience Improvement Program. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPBrowserCustomerExperienceImprovementProgram cmdlet turns on or off the browser Customer Experience Improvement Program 
for collecting software quality metrics For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPBrowserCustomerExperienceImprovementProgram -Farm <SwitchParameter> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<S
witchParameter>]] [-Enable <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPBrowserCustomerExperienceImprovementProgram -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollect
ion>] [-Confirm [<SwitchParameter>]] [-Enable <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPBrowserCustomerExperienceImprovementProgram -SiteSubscription <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCol
lection>] [-Confirm [<SwitchParameter>]] [-Enable <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPBrowserCustomerExperienceImprovementProgram -Farm -Enable
]]>
        </Code>
        <Remarks> This example turns on the browser Customer Experience Improvement Program for the farm </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPBrowserCustomerExperienceImprovementProgram -Farm -Enable:$False
]]>
        </Code>
        <Remarks> This example turns off the browser Customer Experience Improvement Program for the farm </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPWebApplication http://MyOfficeApp1 | Get- SPBrowserCustomerExperienceImprovementProgram -Enable
]]>
        </Code>
        <Remarks> This example turns on the browser Customer Experience Improvement Program for the Web application, MyOfficeApp1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPBusinessDataCatalogMetadataObject </name>
    <synopsis><![CDATA[ Sets the value of a property or attribute of a Business Data Connectivity Metadata Store metadata object. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPBusinessDataCatalogMetadataObject cmdlet sets the value of a property or attribute of a Business Data Connectivity Meta
data Store metadata object For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-PropertyName <String>] [-PropertyValue <PSObject>] [-Remove <SwitchParameter>] [-SettingId <String>] [-WhatIf [<SwitchParam
eter>]] [<CommonParameters>]
Set-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-DisplayName <String>] [-Remove <SwitchParameter>] [-SettingId <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPBusinessDataCatalogMetadataObject -Identity <MetadataObject> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchPa
rameter>]] [-PropertyName <String>] [-Remove <SwitchParameter>] [-Remove <SwitchParameter>] [-SettingId <String>] [-WhatIf [<SwitchParam
eter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$objectToSetOn = Get-SPBusinessDataCatalogMetadataObject -Namespace "ContosoDatabase" -Name "ContosoDatabase" -BdcObjectType "LobS
ystemInstance" -ServiceContext http://contoso
]]>
        </Code>
        <Remarks>
          This example creates a property on the LobSystemInstance (External System Instance) of name ContosoDatabase. The property has the
          name ShowInSearchUI and a value of True
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPBusinessDataCatalogMetadataObject -Identity $objectToSetOn -PropertyName "ShowInSearchUI" -PropertyValue "True"
]]>
        </Code>
        <Remarks>
          This example creates a property on the LobSystemInstance (External System Instance). The namespace parameter must be the name of
          the instance's LobSystem (External System). In this example, they share the same name
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPBusinessDataCatalogServiceApplication </name>
    <synopsis><![CDATA[ Sets global properties for a Business Data Connectivity service application in the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPBusinessDataCatalogServiceApplication cmdlet sets global properties for a Business Data Connectivity service applicatio
n in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPBusinessDataCatalogServiceApplication -Identity <SPServiceApplicationPipeBind> [-ApplicationPool <SPIisWebServiceApplicationPool>]
 [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCredential>] [-DatabaseName <S
tring>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-FailoverDatabaseServer <String>] [-
Name <String>] [-Sharing <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPBusinessDataCatalogServiceApplication -Identity $serviceApplication -FailoverDatabaseServer "CONTOSO\Backup"
]]>
        </Code>
        <Remarks> This example sets the failover database server to CONTOSO\Backup for the given service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPBusinessDataCatalogThrottleConfig </name>
    <synopsis><![CDATA[ Sets the throttling configuration for a Business Data Connectivity Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPBusinessDataCatalogThrottleConfig cmdlet sets the throttling configuration for a Business Data Connectivity Service app
lication For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPBusinessDataCatalogThrottleConfig -Default <Int32> -Identity <ThrottleConfig> -Maximum <Int32> [-AssignmentCollection <SPAssignmen
tCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPBusinessDataCatalogThrottleConfig -Enforced <SwitchParameter> -Identity <ThrottleConfig> [-AssignmentCollection <SPAssignmentColle
ction>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPBusinessDataCatalogThrottleConfig -Scope Database -ThrottleType Items -ServiceApplicationProxy $contosoServAppProxy | Set-SP
BusinessDataCatalogThrottleConfig -Maximum 1000000000 -Default 500000
]]>
        </Code>
        <Remarks>
          This example sets the database item throttling to values of 1000000000 maximum and 500000 default for the given service applicati
          on
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPCentralAdministration </name>
    <synopsis><![CDATA[ Sets the port for the SharePoint Central Administration Web site. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPCentralAdministration cmdlet sets the port for the Central Administration site For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPCentralAdministration -Port <Int32> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<Swi
tchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPCentralAdministration -Port 8282
]]>
        </Code>
        <Remarks> This example sets the port for the Central Administration web application on the local farm to 8282 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPClaimProvider </name>
    <synopsis><![CDATA[ Updates registration of a claims provider. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPClaimProvider cmdlet updates registration of a claims provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPClaimProvider [-Identity] <SPClaimProviderPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Default <SwitchParameter>] 
[-Enabled <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPClaimProvider -Identity "12345678-90ab-cdef-1234-567890bcdefgh"
]]>
        </Code>
        <Remarks> This example turns off the specified claim provider </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPContentDatabase </name>
    <synopsis><![CDATA[ Sets global properties of a SharePoint content database. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPContentDatabase cmdlet sets global properties of a SharePoint content database For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParamet
er>]] [-MaxSiteCount <Int32>] [-Status <Online | Disabled | Offline | Unprovisioning | Provisioning | Upgrading>] [-WarningSiteCount <In
t32>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE 1--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDatabase http://contoso.com | Set-SPContentDatabase -MaxSiteCount 1
]]>
        </Code>
        <Remarks> This example sets the MaxSiteCount for the content database that contains contoso.com to 1 </Remarks>
      </example>
      <example>
        <title> ---------------EXAMPLE 2--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDatabase -WebApplication http://sitename | Set-SPContentDatabase -WarningSiteCount $null
]]>
        </Code>
        <Remarks> This example clears the WarningSiteCount for all databases in the sitename Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPContentDeploymentJob </name>
    <synopsis><![CDATA[ Sets properties of a content deployment job. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPContentDeploymentJob cmdlet sets the properties of a content deployment job For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPContentDeploymentJob -Identity <SPContentDeploymentJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switc
hParameter>]] [-Description <String>] [-EmailAddresses <String[]>] [-EmailNotifications <None | SendEmailOnFailure | SendEmailOnSuccess 
| SendEmailOnAlways>] [-HostingSupportEnabled <SwitchParameter>] [-IncrementalEnabled <SwitchParameter>] [-Name <String>] [-Schedule <St
ring>] [-ScheduleEnabled <SwitchParameter>] [-Scope <SPWebPipeBind[]>] [-SqlSnapshotSetting <None | CreateNew>] [-WhatIf [<SwitchParamet
er>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDeploymentJob "Job 1" | Set-SPContentDeploymentJob -Schedule "hourly between 0 and 59" -ScheduleEnabled:$true
]]>
        </Code>
        <Remarks> This example sets the deployment job called Job 1 to run hourly </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPContentDeploymentPath </name>
    <synopsis><![CDATA[ Sets properties of a content deployment path. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPContentDeploymentPath cmdlet sets the properties of a content deployment path for a content deployment job For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPContentDeploymentPath -Identity <SPContentDeploymentPathPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Authenticatio
n <Basic | Windows>] [-CompressionEnabled <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DeploySecurityInformation <None | WssOnly 
| All>] [-DeployUserNamesEnabled <SwitchParameter>] [-Description <String>] [-DestinationCentralAdministrationURL <Uri>] [-EventReceiver
sEnabled <SwitchParameter>] [-KeepTemporaryFilesOptions <Never | Always | Failure>] [-Name <String>] [-PathAccount <PSCredential>] [-Pat
hEnabled <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------EXAMPLE------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDeploymentPath "Path 1" | Set-SPContentDeploymentPath -PathEnabled:$false
]]>
        </Code>
        <Remarks> This example sets the deployment path Path 1 to be disabled </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPCustomLayoutsPage </name>
    <synopsis><![CDATA[ Maps a new path for a custom layout page. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPCustomLayoutsPage cmdlet maps a new path for a custom layouts page in a Web application. To remove the mapping for a cu
stom layouts page, use the Reset parameter instead of the RelativePath parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPCustomLayoutsPage -Identity <None | AccessDenied | Confirmation | Error | Login | RequestAccess | Signout | WebDeleted> -RelativeP
ath <String> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] 
[-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPCustomLayoutsPage -Identity <None | AccessDenied | Confirmation | Error | Login | RequestAccess | Signout | WebDeleted> -Reset <Sw
itchParameter> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]
] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPCustomLayoutsPage -Identity "_layouts/accessdenied.aspx" -RelativePath "/_layouts/custompages/myaccessdenied.aspx" -WebAppli
cation "http://server_name/mywebapp"
]]>
        </Code>
        <Remarks> This example maps the specified path for the AccessDenied layout page in the Web application "http://server_name/mywebapp" </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPDataConnectionFile </name>
    <synopsis><![CDATA[ Sets properties of a data connection file. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPDataConnectionFile cmdlet sets the properties of the data connection file specified in the Identity parameter For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPDataConnectionFile -Identity <SPDataConnectionFilePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Category <String>] 
[-Confirm [<SwitchParameter>]] [-Description <String>] [-DisplayName <String>] [-WebAccessible <String>] [-WhatIf [<SwitchParameter>]] [
<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPDataConnectionFile -Identity "sample.udcx" -Category "Temp"
]]>
        </Code>
        <Remarks> This example updates the Category of the specified .udcx file </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPDataConnectionFile -Identity "sample.udcx" -DisplayName "NewDisplayName"
]]>
        </Code>
        <Remarks> This example updates the DisplayName of the specified .udcx file </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Sample.udcx" | Set-SPDataConnectionFile -Category "Temp"
]]>
        </Code>
        <Remarks> This example updates the Category of the specified .udcx file </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 4----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDataConnectionFile | where {$_.Category -eq "Category1"}  | Set-SPDataConnectionFile -Category "Category2"
]]>
        </Code>
        <Remarks>
          This example updates the Category field for the collection of .udcx files that are returned from a query used by the Get-SPDataCo
          nnectionFile cmdlet
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPDesignerSettings </name>
    <synopsis><![CDATA[ Sets Microsoft SharePoint Designer 2010 features. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPDesignerSettings cmdlet sets SharePoint Designer 2010 features on a specified Web application when the WebApplicaton is
 used For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPDesignerSettings [-WebApplication] <SPWebApplicationPipeBind> [-AllowDesigner <$true | $false>] [-AllowMasterPageEditing <$true | 
$false>] [-AllowRevertFromTemplate <$true | $false>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-S
howURLStructure <$true | $false>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPDesignerSettings -WebApplication http://constoso -AllowRevertFromTemplate $False -AllowMasterPageEditing $False
]]>
        </Code>
        <Remarks> This example disables the ability to detach pages from existing site definitions and to edit master pages and page layouts </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPDiagnosticConfig </name>
    <synopsis><![CDATA[ Sets diagnostic configuration settings on the farm. ]]></synopsis>
    <description>
      <![CDATA[ Use the Set-SPDiagnosticConfig cmdlet to set diagnostic configuration settings on the entire farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPDiagnosticConfig [-AllowLegacyTraceProviders <SwitchParameter>] [-AssignmentCollection <SPAssignmentCollection>] [-CustomerExperie
nceImprovementProgramEnabled <SwitchParameter>] [-DaysToKeepLogs <Int32>] [-DownloadErrorReportingUpdatesEnabled <SwitchParameter>] [-Er
rorReportingAutomaticUploadEnabled <SwitchParameter>] [-ErrorReportingEnabled <SwitchParameter>] [-EventLogFloodProtectionEnabled <Switc
hParameter>] [-EventLogFloodProtectionNotifyInterval <Int32>] [-EventLogFloodProtectionQuietPeriod <Int32>] [-EventLogFloodProtectionThr
eshold <Int32>] [-EventLogFloodProtectionTriggerPeriod <Int32>] [-InputObject <PSObject>] [-LogCutInterval <Int32>] [-LogDiskSpaceUsageG
B <Int32>] [-LogLocation <String>] [-LogMaxDiskSpaceUsageEnabled <SwitchParameter>] [-ScriptErrorReportingDelay <Int32>] [-ScriptErrorRe
portingEnabled <SwitchParameter>] [-ScriptErrorReportingRequireAuth <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>set-spdiagnosticconfig -errorReportingEnable -DownloadErrorReportingUpdatesEnabled:$false -DaysToKeepLog  60
]]>
        </Code>
        <Remarks> This example set the number of days to keep the log file to 60 </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$L = get-spdiagnosticconfig

C:\PS>$L.CustomerExperienceImprovementProgramEnabled = $false

C:\PS>$L.LogCutInterval = 60

C:\PS>$L | Set-SPDiagnosticConfig
]]>
        </Code>
        <Remarks> This example enables ErrorReporting, disables DownloadErrorReportingUpdates, and then sets DaysToKeepLog to 60 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPDiagnosticsProvider </name>
    <synopsis><![CDATA[ Enables a diagnostics provider and updates its retention policy. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPDiagnosticsProvider cmdlet enables a diagnostics provider and updates its retention policy For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPDiagnosticsProvider [-Identity] <SPDiagnosticsProviderPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switc
hParameter>]] [-DaysRetained <Int32>] [-Enable <SwitchParameter>] [-MaxTotalSizeInBytes <Int64>] [-WhatIf [<SwitchParameter>]] [<CommonP
arameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDiagnosticsProvider job-diagnostics-event-log-provider | Set-SPDiagnosticsProvider -Enable:$false

C:\PS>Get-SPDiagnosticsProvider job-diagnostics-event-log-provider
]]>
        </Code>
        <Remarks> This example disables the event log diagnostics provider </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPDiagnosticsProvider job-diagnostics-event-log-provider | Set-SPDiagnosticsProvider -Enable -DaysRetained 10

C:\PS>Get-SPDiagnosticsProvider job-diagnostics-event-log-provider
]]>
        </Code>
        <Remarks> This example enables the event log diagnostics provider and changes its retention policy to 10 days </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchAdministrationComponent </name>
    <synopsis><![CDATA[ Sets properties of an administration component for a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchAdministrationComponent cmdlet updates properties of an AdministrationComponent object for a search ser
vice application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchAdministrationComponent [[-Identity] <AdminComponentPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-SearchServiceInstance 
<SearchServiceInstancePipeBind>] [-StoragePath <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "Sample Search Service Application" admin = Get-SPEnterpriseSearchAdministra
tionComponent -SearchApplication $searchapp
$admin | Set-SPEnterpriseSearchAdministrationComponent -SearchServiceInstance newserver -Force
]]>
        </Code>
        <Remarks> This example moves the administration component to a different server </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchCrawlContentSource </name>
    <synopsis><![CDATA[ Sets the properties of a crawl content source for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchCrawlContentSource cmdlet updates the rules of a crawl content source when the search functionality is 
initially configured and after any new content source is added. This cmdlet is called once to set the incremental crawl schedule for a co
ntent source, and it is called again to set a full crawl schedule For permissions and the most current information about search cmdlets, see the online documentation (http://go.microsoft.com/fwli
nk/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-BDCAppli
cationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm [<SwitchParameter>]] [-CrawlPriority <Nullable>] [-CustomProtocol <
String>] [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Nullable>] [-MaxSiteEnumerationDepth <Nullable>] [-Name <String>] [-Searc
hApplication <SearchServiceApplicationPipeBind>] [-StartAddresses <String>] [-Tag <String>] [-WhatIf [<SwitchParameter>]] [<CommonParame
ters>]
Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-BDCAppli
cationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm [<SwitchParameter>]] [-CrawlPriority <Nullable>] [-CrawlScheduleDay
sOfMonth <Nullable>] [-CrawlScheduleMonthsOfYear <Nullable>] [-CrawlScheduleRepeatDuration <Nullable>] [-CrawlScheduleRepeatInterval <Nu
llable>] [-CrawlScheduleStartDateTime <Nullable>] [-CustomProtocol <String>] [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Nulla
ble>] [-MaxSiteEnumerationDepth <Nullable>] [-MonthlyCrawlSchedule <SwitchParameter>] [-Name <String>] [-ScheduleType <Nullable>] [-Sear
chApplication <SearchServiceApplicationPipeBind>] [-StartAddresses <String>] [-Tag <String>] [-WhatIf [<SwitchParameter>]] [<CommonParam
eters>]
Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-BDCAppli
cationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm [<SwitchParameter>]] [-CrawlPriority <Nullable>] [-CustomProtocol <
String>] [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Nullable>] [-MaxSiteEnumerationDepth <Nullable>] [-Name <String>] [-Remov
eCrawlSchedule <SwitchParameter>] [-ScheduleType <Nullable>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-StartAddresses <S
tring>] [-Tag <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-BDCAppli
cationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm [<SwitchParameter>]] [-CrawlPriority <Nullable>] [-CrawlScheduleDay
sOfWeek <Nullable>] [-CrawlScheduleRepeatDuration <Nullable>] [-CrawlScheduleRepeatInterval <Nullable>] [-CrawlScheduleRunEveryInterval 
<Nullable>] [-CrawlScheduleStartDateTime <Nullable>] [-CustomProtocol <String>] [-LOBSystemSet <String[]>] [-MaxPageEnumerationDepth <Nu
llable>] [-MaxSiteEnumerationDepth <Nullable>] [-Name <String>] [-ScheduleType <Nullable>] [-SearchApplication <SearchServiceApplication
PipeBind>] [-StartAddresses <String>] [-Tag <String>] [-WeeklyCrawlSchedule <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonPar
ameters>]
Set-SPEnterpriseSearchCrawlContentSource [-Identity] <ContentSourcePipeBind> -ScheduleType <Nullable> [-AssignmentCollection <SPAssignme
ntCollection>] [-BDCApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-Confirm [<SwitchParameter>]] [-CrawlPriority <Null
able>] [-CrawlScheduleRepeatDuration <Nullable>] [-CrawlScheduleRepeatInterval <Nullable>] [-CrawlScheduleRunEveryInterval <Nullable>] [
-CrawlScheduleStartDateTime <Nullable>] [-CustomProtocol <String>] [-DailyCrawlSchedule <SwitchParameter>] [-LOBSystemSet <String[]>] [-
MaxPageEnumerationDepth <Nullable>] [-MaxSiteEnumerationDepth <Nullable>] [-Name <String>] [-SearchApplication <SearchServiceApplication
PipeBind>] [-StartAddresses <String>] [-Tag <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$cs = Get-SPEnterpriseSearchCrawlContentSource -SearchApplication $searchapp ""
$cs | Set-SPEnterpriseSearchCrawlContentSource -ScheduleType Full -DailyCrawlSchedule -CrawlScheduleRunEveryInterval 30
$cs | Set-SPEnterpriseSearchCrawlContentSource -ScheduleType Incremental -DailyCrawlSchedule -CrawlScheduleRepeatInterval 60 -CrawlSched
uleRepeatDuration 1440
]]>
        </Code>
        <Remarks>
          This example returns an existing content source ExampleContentSource1, and creates a schedule to run a full crawl every 30 days a
          nd an incremental crawl every hour every day
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchCrawlDatabase </name>
    <synopsis><![CDATA[ Sets properties of a crawl database for a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchCrawlDatabase cmdlet sets properties of a specified crawl database for a search service application. A 
crawl database stores crawl history for a search service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchCrawlDatabase [-Identity] <CrawlStorePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switch
Parameter>]] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-Failo
verDatabaseServer <String>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-Shared <SwitchParameter>] [-WhatIf [<SwitchParamet
er>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp
Set-SPEnterpriseSearchCrawlDatabase -Identity SearchApp_CrawlStore
-SearchApplication $searchApp -FailoverDatabaseServer \\failoverServer
]]>
        </Code>
        <Remarks> This example sets the failover database server for the crawl database, SearchApp_CrawlStore, to the \\failoverServer server </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchCrawlRule </name>
    <synopsis><![CDATA[ Sets properties for a crawl rule. ]]></synopsis>
    <description>
      <![CDATA[ A search administrator runs the Set-SPEnterpriseSearchCrawlRule cmdlet at initial search configuration or any other time, to set 
and/or update various attributes of a crawl rule For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchCrawlRule [-Identity] <CrawlRulePipeBind> [-AccountName <String>] [-AccountPassword <SecureString>] [-AssignmentCo
llection <SPAssignmentCollection>] [-AuthenticationType <Nullable>] [-Confirm [<SwitchParameter>]] [-ContentClass <String>] [-CrawlAsHtt
p <Nullable>] [-FollowComplexUrls <Nullable>] [-IsAdvancedRegularExpression <Nullable>] [-PluggableSecurityTimmerId <Nullable>] [-Priori
ty <Nullable>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-SuppressIndexing <Nullable>] [-Type <Nullable>] [-WhatIf [<Swit
chParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$crawlRule = Get-SPEnterpriseSearchCrawlRule -Identity
file://fileserver/root -SearchApplication mySearchServiceApp
Set-SPEnterpriseSearchCrawlRule -Identity $crawlRule -Type "ExclusionRule"
]]>
        </Code>
        <Remarks>
          This example sets the type of the crawl rule pertaining to the URL, file://fileserver/root, to exclude this path from future craw
          ls
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchCrawlTopology </name>
    <synopsis><![CDATA[ Sets the properties of a crawl topology on a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchCrawlTopology cmdlet updates the properties of a specified crawl topology. A crawl topology contains th
e crawl component collection for a topology on a shared search application For permissions and the most current information about search cmdlets, see the online documentation (http://go.microsoft.com/fwli
nk/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchCrawlTopology [-Identity] <CrawlTopologyPipeBind> [-Active <SwitchParameter>] [-AssignmentCollection <SPAssignment
Collection>] [-Confirm [<SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$topo = Get-SPEnterpriseSearchCrawlTopology -SearchApplication $searchapp -Identity 00000000-0000-0000-0000-000000000000
New-SPEnterpriseSearchCrawlComponent -SearchApplication $searchapp -CrawlTopology $topo -CrawlDatabase "Sample_Search_Service_Applicatio
n_CrawlStoreDB" -SearchServiceInstance servername -IndexLocation d:\crawlshare
$topo | Set-SPEnterpriseSearchCrawlTopology -Active
]]>
        </Code>
        <Remarks> This example retrieves the inactive crawl topology, adds a search component to it, and activates the crawl topology </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchIndexPartition </name>
    <synopsis><![CDATA[ Sets properties of an index partition for a query topology. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchIndexPartition cmdlet updates properties of an index partition. Index partitions define how document id
entifiers (IDs) are mapped to the query components for full-text user queries for a shared search application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchIndexPartition [-Identity] <IndexPartitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<S
witchParameter>]] [-PropertyDatabase <PropertyStorePipeBind>] [-QueryTopology <QueryTopologyPipeBind>] [-SearchApplication <SearchServic
eApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1" 
$qtopo = Get-SPEnterpriseSearchQueryTopology -SearchApplication $searchapp
$qtopo2 = New-SPEnterpriseSearchQueryTopology -SearchApplication $searchapp -QueryTopology $qtopo -Clone 
$index = Get-SPEnterpriseSearchIndexPartition -QueryTopology $qtopo2
$newpropstore = New-SPEnterpriseSearchPropertyDatabase -SearchApplication $searchapp -DatabaseName New_Property_Database
$index | Set-SPEnterpriseSearchIndexPartition -PropertyDatabase New_Property_Database
$qtopo2 | Set-SPEnterpriseSearchQueryTopology -Active
]]>
        </Code>
        <Remarks> This example modifies the index partition by replacing the property database with a new database </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchMetadataCategory </name>
    <synopsis><![CDATA[ Sets properties of a crawled property category for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchMetadataCategory cmdlet updates properties of a crawled property category when the search functionality
 is initially configured and after a new crawled property category is discovered during a crawl. SPEnterpriseSearchMetadataCategory repre
sents a category in the enterprise search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchMetadataCategory [-Identity] <CategoryPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-AutoCreateNewMa
nagedProperties <Nullable>] [-Confirm [<SwitchParameter>]] [-DiscoverNewProperties <Nullable>] [-MapToContents <Nullable>] [-Name <Strin
g>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$cat = Get-SPEnterpriseSearchMetadataCategory -Identity test -SearchApplication $searchapp
$cat | Set-SPEnterpriseSearchMetadataCategory -Name test2
]]>
        </Code>
        <Remarks> This example changes the name of the metadata category from test to test2 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchMetadataCrawledProperty </name>
    <synopsis><![CDATA[ Sets the properties of a metadata crawled property for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchMetadataCrawledProperty cmdlet updates properties of a crawled property when the search functionality i
s initially configured and after any new crawled property is added to create the rules for the crawled property. SPEnterpriseSearchMetada
taCrawledProperty represents a crawled property in the enterprise search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchMetadataCrawledProperty [-Identity] <CrawledPropertyPipeBind> -IsMappedToContents <Nullable> [-AssignmentCollectio
n <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$prop = Get-SPEnterpriseSearchMetadataCrawledProperty -Name testcrawledproperty -SearchApplication $searchapp
$prop | Set-SPEnterpriseSearchMetadataCrawledProperty -IsMappedToContents $False
]]>
        </Code>
        <Remarks> This example changes the attribute that maps the crawled property to managed properties to False </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchMetadataManagedProperty </name>
    <synopsis><![CDATA[ Sets the properties of a metadata managed property. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchMetadataManagedProperty cmdlet updates the properties of a managed property. This cmdlet is used typica
lly to change the name or description of a managed property. SPEnterpriseSearchMetadataManagedProperty represents a managed property in t
he enterprise search metadata property schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchMetadataManagedProperty [-Identity] <ManagedPropertyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-C
onfirm [<SwitchParameter>]] [-DefaultForQueryIndependentRank <Nullable>] [-Description <String>] [-EnabledForQueryIndependentRank <Nulla
ble>] [-EnabledForScoping <Nullable>] [-FullTextQueriable <Nullable>] [-IncludeInMd5 <Nullable>] [-Name <String>] [-NameNormalized <Null
able>] [-NoWordBreaker <Nullable>] [-RemoveDuplicates <Nullable>] [-RespectPriority <Nullable>] [-Retrievable <Nullable>] [-SearchApplic
ation <SearchServiceApplicationPipeBind>] [-UserFlags <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity testmanagedproperty
$mp | Set-SPEnterpriseSearchMetadataManagedProperty -EnabledForScoping $True
]]>
        </Code>
        <Remarks> This example enables the managed property to be used in a scope </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchMetadataMapping </name>
    <synopsis><![CDATA[ Sets the properties of a managed property mapping for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchMetadataMapping cmdlet updates properties of a managed property mapping. SPEnterpriseSearchMetadataMapp
ing represents a snapshot of a mapping between a managed property and one or more crawled properties in the enterprise search metadata pr
operty schema For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchMetadataMapping [-Identity] <MappingPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchP
arameter>]] [-CrawledProperty <CrawledPropertyPipeBind>] [-ManagedProperty <ManagedPropertyPipeBind>] [-SearchApplication <SearchService
ApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchapp = Get-SPEnterpriseSearchServiceApplication "SearchApp1"
$mp = Get-SPEnterpriseSearchMetadataManagedProperty -SearchApplication $searchapp -Identity testmanagedproperty
$prop = Get-SPEnterpriseSearchMetadataCrawledProperty -SearchApplication $searchapp -Name testcrawledproperty
Set-SPEnterpriseSearchMetadataMapping -SearchApplication $searchapp -ManagedProperty $mp
]]>
        </Code>
        <Remarks>
          This example sets the mapping between the managed property testmanagedproperty and the crawled property testcrawledproperty for t
          he search service application SearchApp1
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchPropertyDatabase </name>
    <synopsis><![CDATA[ Modifies properties for a property store. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchPropertyDatabase cmdlet modifies properties for a specified property store in the property store collec
tion. A property store stores metadata about content for a search service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchPropertyDatabase [-Identity] <PropertyStorePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<
SwitchParameter>]] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [
-FailoverDatabaseServer <String>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParamete
rs>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp
Set-SPEnterpriseSearchPropertyDatabase -Identity PropertyStore-1
-SearchApplication $searchApp -FailoverDatabaseServer \\failoverServer
]]>
        </Code>
        <Remarks> This example sets the failover database server for the property database, PropertyStore-1, to the \\failoverServer server </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchQueryAuthority </name>
    <synopsis><![CDATA[ Sets the properties of an authoritative page for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchQueryAuthority cmdlet updates properties of an authoritative page and adjusts the query rank of an auth
oritative page. SPEnterpriseSearchQueryAuthority represents authoritative sites that rank higher in relevance than demoted sites, which a
re de-emphasized in relevance For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchQueryAuthority [-Identity] <AuthorityPagePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Sw
itchParameter>]] [-Level <Nullable>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParam
eters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPEnterpriseSearchQueryAuthority -Identity http://contoso.com -Level 0.5 -SearchApplication MySSA
]]>
        </Code>
        <Remarks> This example adjusts the authoritative level of the URL http://contoso.com to 0.5 on the search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchQueryComponent </name>
    <synopsis><![CDATA[ Modifies properties for a query component. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchQueryComponent cmdlet updates properties for a query component For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchQueryComponent [-Identity] <QueryComponentPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<S
witchParameter>]] [-FailoverOnly <Nullable>] [-QueryTopology <QueryTopologyPipeBind>] [-SearchApplication <SearchServiceApplicationPipeB
ind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$searchApp = Get-SPEnterpriseSearchServiceApplication mySearchServiceApp
Get-SPEnterpriseSearchQueryTopology -SearchApplication $searchApp
Get-SPEnterpriseSearchQueryComponent -QueryTopology $qt | 
Set-SPEnterpriseSearchQueryComponent -FailoverOnly $true
]]>
        </Code>
        <Remarks>
          This example sets the query component of the search service application, mySearchServiceApp, to serve as a failover-only query co
          mponent
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchQueryKeyword </name>
    <synopsis><![CDATA[ Sets the properties of a keyword term for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchQueryKeyword cmdlet updates properties and rules of a keyword term. A query keyword is a query componen
t of a query topology. SPEnterpriseSearchQueryKeyword represents relevance setting through keywords For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchQueryKeyword [-Identity] <KeywordPipeBind> -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>]
 [-Confirm [<SwitchParameter>]] [-Contact <String>] [-Definition <String>] [-EndDate <Nullable>] [-ReviewDate <Nullable>] [-StartDate <N
ullable>] [-Term <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchQueryKeyword -Identity Engineering -Site http://myserver/sites/engineering | Set-SPEnterpriseSearchQueryKeyw
ord -StartDate "12/25/2009" -EndDate "12/24/2010" -Site http://myserver/sites/engineering
]]>
        </Code>
        <Remarks>
          This example gets a reference to the keyword with the term Engineering from the site http://myserver/sites/engineering, and sets
          the start dates and end dates for the keyword
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchQueryScope </name>
    <synopsis><![CDATA[ Sets the properties of a query results scope for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchQueryScope cmdlet updates properties of a shared scope. SPEnterpriseSearchQueryScope represents a query
 results scope used by all shared search applications on the farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchQueryScope [-Identity] <ScopePipeBind> -AlternateResultsPage <String> [-AssignmentCollection <SPAssignmentCollecti
on>] [-CompilationType <Nullable>] [-Confirm [<SwitchParameter>]] [-Description <String>] [-DisplayInAdminUI <Nullable>] [-Name <String>
] [-SearchApplication <SearchServiceApplicationPipeBind>] [-Url <Uri>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPenterpriseSearchServiceApplication -Identity MySSA
Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa | Set-SPEnterpriseSearchQueryScope -Description "Business c
ritical sites to index" -CompilationType 1 -AlternateResultsPage http://altServer
]]>
        </Code>
        <Remarks>
          This example obtains a reference to the scope named MustCrawl on the search service application named MySSA, and changes the desc
          ription, compilation type, and alternate access URL
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchQueryScopeRule </name>
    <synopsis><![CDATA[ Sets the properties of a shared scope rule for a query scope. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchQueryScopeRule cmdlet updates the properties of a query scope. SPEnterpriseSearchQueryScopeRule represe
nts a query results scope rule that can be applied to a scope For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchQueryScopeRule [-Identity] <ScopeRulePipeBind> -Url <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Confi
rm [<SwitchParameter>]] [-FilterBehavior <String>] [-ManagedPropertyName <String>] [-MatchingString <String>] [-PropertyValue <String>] 
[-Scope <ScopePipeBind>] [-SearchApplication <SearchServiceApplicationPipeBind>] [-UrlScopeRuleType <String>] [-WhatIf [<SwitchParameter
>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA"
$scope = Get-SPEnterpriseSearchQueryScope -Identity MustCrawl -SearchApplication $ssa
Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url http://criticalSite | Set-SPEnterpriseSearchQueryScopeRule -Url http://criticalS
ite -UrlScopeRuleType Url
]]>
        </Code>
        <Remarks> This example gets a reference to a scope rule for the URL http://criticalSite and sets its rule type to Url </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchQueryTopology </name>
    <synopsis><![CDATA[ Sets the properties of a query topology for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchQueryTopology cmdlet updates properties of a query topology. A topology can contain multiple query topo
logies when a query component or index partition is added to or deleted from a topology For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchQueryTopology [-Identity] <QueryTopologyPipeBind> [-Active <SwitchParameter>] [-AssignmentCollection <SPAssignment
Collection>] [-Confirm [<SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssi = Get-SPEnterpriseSearchServiceInstance
$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA
$newQueryTopology = $ssa | New-SPEnterpriseSearchQueryTopology -Partitions 1
$ip = Get-SPEnterpriseSearchIndexPartition -QueryTopology $newQueryTopology
$queryComponent = New-SPEnterpriseSearchQuerycomponent -QueryTopology $newQueryTopology -IndexPartition $ip -SearchServiceInstance $ssi
$newQueryTopology | Set-SPEnterpriseSearchQueryTopology -Active
]]>
        </Code>
        <Remarks>
          This example creates a new query topology and query component, adds the new query topology to a search service application and se
          ts it as the active query topology
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchRankingModel </name>
    <synopsis><![CDATA[ Sets the properties of a ranking model for a shared search application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchRankingModel cmdlet updates properties of a ranking model for a query service application. The name, de
scription, and identifier (ID) for a ranking model are contained in the .xml file specified in RankingModelXML. If the Identity parameter
 is not specified or the identity does not match any of the ranking models in the collection, an exception is thrown and the default rank
ing model is used For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchRankingModel [-Identity] <RankingModelPipeBind> -RankingModelXML <String> [-AssignmentCollection <SPAssignmentColl
ection>] [-Confirm [<SwitchParameter>]] [-SearchApplication <SearchServiceApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonPa
rameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$rankingModel = Get-SPEnterpriseSearchServiceApplication -Identity "MySSA" | Get-SPEnterpriseSearchRankingModel
$rankingModel[0] |  Set-SPEnterpriseSearchRankingModel -RankingModelXML newModel.xml
]]>
        </Code>
        <Remarks>
          This example reconfigures the first ranking model from the search service application to the configuration contained in newModel.
          xml
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchService </name>
    <synopsis><![CDATA[ Sets the properties of a search service for a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchService cmdlet updates properties of a search service for a farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchService [[-Identity] <SearchServicePipeBind>] [-AcknowledgementTimeout <String>] [-AssignmentCollection <SPAssignm
entCollection>] [-Confirm [<SwitchParameter>]] [-ConnectionTimeout <String>] [-ContactEmail <String>] [-IgnoreSSLWarnings <String>] [-In
ternetIdentity <String>] [-PerformanceLevel <String>] [-ProxyType <String>] [-ServiceAccount <String>] [-ServicePassword <SecureString>]
 [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$password = Read-Host -AsSecureString
**********
Set-SPEnterpriseSearchService -IgnoreSSLWarnings $true -ServiceAccount contoso\adminAccount -ServicePassword $password
]]>
        </Code>
        <Remarks> This example configures the search service to ignore SSL warnings, and changes the service account for the search service </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Sets the properties of a search service application for a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchServiceApplication cmdlet updates properties of a search service application. SPEnterpriseSearchService
Application represents a self-contained aggregation of indexed content and properties available for search, and provides an anchor class 
for setting global search properties. A search application can include multiple search service applications For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> [-AdminApplicationPool <SPIisWebServiceApplicati
onPoolPipeBind>] [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm 
[<SwitchParameter>]] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>]
 [-DefaultContentAccessAccountName <String>] [-DefaultContentAccessAccountPassword <SecureString>] [-DefaultSearchProvider <Nullable>] [
-DiacriticSensitive <String>] [-FailoverDatabaseServer <String>] [-VerboseQueryMonitoring <String>] [-WhatIf [<SwitchParameter>]] [<Comm
onParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPEnterpriseSearchServiceApplication -Identity MySSA -VerboseQueryMonitoring True
]]>
        </Code>
        <Remarks> This example turns on verbose query logging in the search service application named MySSA </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchServiceApplicationProxy </name>
    <synopsis><![CDATA[ Sets properties of a search service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchServiceApplicationProxy cmdlet updates properties of a site administration service application proxy fo
r a search application. SPEnterpriseSearchServiceApplicationProxy represents the proxy for search site administration functionality. One 
search service application proxy exists for each search application on a farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchServiceApplicationProxy [-Identity] <SearchServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmentCo
llection>] [-Confirm [<SwitchParameter>]] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceApplicationProxy -Identity SsaProxy | Set- SPEnterpriseSearchServiceApplicationProxy -Name ContosoSea
rchProxy
]]>
        </Code>
        <Remarks> This example sets the display name of a search service application proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPEnterpriseSearchServiceInstance </name>
    <synopsis><![CDATA[ Sets the properties of a search service instance. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPEnterpriseSearchServiceInstance cmdlet updates properties of the search service instance for a farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPEnterpriseSearchServiceInstance [-Identity] <SearchServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Con
firm [<SwitchParameter>]] [-DefaultIndexLocation <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceInstance | Set-SPEnterpriseSearchServiceInstance -DefaultIndexLocation E:\SearchData
]]>
        </Code>
        <Remarks> This example sets the index location for the search service instance to the path e:\SearchData </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPFarmConfig </name>
    <synopsis><![CDATA[ Sets a global property or a collection of global properties for the local farm. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPFarmConfig cmdlet updates a collection of global settings for the local farm that are not members of the SPFarm object.
 Use the Get-SPFarmConfig cmdlet to read global settings for the local farm and to create a new PSCustomObject object from the collection
 of properties returned from the local farm, and then add this object to the pipeline. Modify the PSCustomObject object and pass it to th
e Set-SPFarmConfig cmdlet to change the parameter values The properties collected in the PSCustomObject object must be farm-wide settings, and must be configurable only once for the enti
re farm. The parameter name added to the PSCustomObject object must match exactly the input parameter name for the Set-the SPFarmConfig c
mdlet For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPFarmConfig [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DataFormWebPartAutoRefreshEnabled <$t
rue | $false>] [-Force <SwitchParameter>] [-InstalledProductsRefresh <SwitchParameter>] [-ServiceConnectionPointBindingInformation <Stri
ng>] [-ServiceConnectionPointDelete <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [-WorkflowBatchSize <Int32>] [-WorkflowEventDeliver
yTimeout <Int32>] [-WorkflowPostponeThreshold <Int32>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE-------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$a = Get-SPFarmConfigPS> $a.AjaxTimeout = 200PS> $a | Set-SPFarmConfig
]]>
        </Code>
        <Remarks>
          This example uses the Get-SPFarmConfig cmdlet to add the Ajax Timeout setting to the PSCustomObject object, sets the value for Aj
          ax Timeout, and then passes PSCustomObject to the Set-SPFarmConfig cmdlet to change the Ajax Timeout setting. Ajax Timeout, a farm-wide s
          etting, is a member of the SPWebService object and cannot be accessed by using a Windows PowerShell cmdlet You can perform the same operations with either of the following commands
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPInfoPathFormsService </name>
    <synopsis><![CDATA[ Sets parameters for InfoPath Forms Services in Microsoft SharePoint Server 2010. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPInfoPathFormsService cmdlet modifies the settings for InfoPath Forms Services in SharePoint Server 2010 For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPInfoPathFormsService [-ActiveSessionTimeout <Nullable>] [-AllowEmbeddedSqlForDataConnections <String>] [-AllowUdcAuthenticationFor
DataConnections <String>] [-AllowUserFormBrowserEnabling <String>] [-AllowUserFormBrowserRendering <String>] [-AllowUserFormCrossDomainD
ataConnections <String>] [-AllowViewState <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-De
faultDataConnectionTimeout <Nullable>] [-Identity <SPFormsServicePipeBind>] [-MaxDataConnectionResponseSize <Nullable>] [-MaxDataConnect
ionRoundTrip <Nullable>] [-MaxDataConnectionTimeout <Nullable>] [-MaxFormLoadTime <Nullable>] [-MaxPostbacksPerSession <Nullable>] [-Max
SizeOfUserFormState <Nullable>] [-MaxUserActionsPerPostback <Nullable>] [-MemoryCacheSize <Nullable>] [-RequireSslForDataConnections <St
ring>] [-ViewStateThreshold <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPInfoPathFormsService -AllowUserFormBrowserEnabling $true -AllowUserFormBrowserRendering $false
]]>
        </Code>
        <Remarks> This example modifies the AllowUserFormBrowserEnabling and AllowUserFormBrowserRendering parameter values </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPInfoPathFormsService -AllowViewState $true -ViewStateThreshold 40961
]]>
        </Code>
        <Remarks> This example modifies the AllowViewState and ViewStateThreshold parameter values </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPInfoPathFormTemplate </name>
    <synopsis><![CDATA[ Sets properties of a Microsoft InfoPath 2010 form template. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPInfoPathFormsTemplate cmdlet modifies the category of an InfoPath 2010 form template or to specify the browser streams 
for the form template For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPInfoPathFormTemplate -Identity <SPFormTemplatePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Category <String>] [-Co
nfirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-InfoPathFormTemplate -Identity "Sample.xsn" -Category "WorkFlowCategory"
]]>
        </Code>
        <Remarks> This example modifies the category property of a form template for a specified name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPInfoPathWebServiceProxy </name>
    <synopsis><![CDATA[ Sets parameters for an existing SharePoint Web service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPInfoPathWebServiceProxy cmdlet configures exposed parameters for an existing SharePoint Web application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPInfoPathWebServiceProxy -Identity <SPWebServiceProxyPipeBind> [-AllowForUserForms <String>] [-AllowWebServiceProxy <String>] [-Ass
ignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPInfoPathWebServiceProxy -Identity "http://server_name" -AllowWebServiceProxy $true
]]>
        </Code>
        <Remarks> This example sets the Web service proxy for a Web application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPLogLevel </name>
    <synopsis><![CDATA[ Sets the trace and event level for a set of categories. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPLogLevel cmdlet sets the Windows event logging and trace logging levels for one or more diagnostic logging categories r
egistered in the farm. If an event or trace associated with a category occurs, but is less severe than that category's logging level, the
 event or trace is not written to the event log or the trace log. If an event or trace associated with a category occurs and is equally s
evere or more severe than that category's logging level, the event or trace is written to the event log or the trace log For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPLogLevel [-AssignmentCollection <SPAssignmentCollection>] [-EventSeverity <String>] [-Identity <String[]>] [-InputObject <PSObject
>] [-TraceSeverity <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>set-sploglevel -TraceSeverity Monitorable
]]>
        </Code>
        <Remarks> This example sets the TraceSeverity values for all categories to Monitorable </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPLogLevel -TraceSeverity High -EventSeverity Warning -Identity "Cat1"
]]>
        </Code>
        <Remarks> This example sets the EventSeverity and TraceSeverity values for a single category </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 3----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>"Cat1", "Cat2", "Cat3" | Set-SPLogLevel -EventSeverity Error
]]>
        </Code>
        <Remarks> This example sets the EventSeverity values for multiple categories </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 4----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPLogLevel -EventSeverity Warning -Identity "AreaName:*"
]]>
        </Code>
        <Remarks> This example sets the EventSeverity values for all categories in the same area </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPManagedAccount </name>
    <synopsis><![CDATA[ Configures the managed account. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPManagedAccount cmdlet sets the properties on the given managed account You can use this cmdlet to change the password expiration and notification settings for the managed account: Use the default para
meter set. Additionally, you can use this cmdlet to change the password for the managed account to automatically generated passwords on a
 set schedule: Use the parameter set that includes the AutoGeneratePassword parameter. You can also use this cmdlet to change the passwor
d for the managed account to a new value, known to the administrator: Use the parameter set that includes the SetNewPassword parameter. F
inally, you can use this cmdlet to change the password for the managed account to an existing value that has been already been changed in
 Active Directory Domain Services (AD DS): Use the parameter set that includes the UseExistingPassword parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter
>]] [-EmailNotification <Int32>] [-PreExpireDays <Int32>] [-Schedule <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-AutoGeneratePassword <Swi
tchParameter>] [-Confirm [<SwitchParameter>]] [-EmailNotification <Int32>] [-PreExpireDays <Int32>] [-Schedule <String>] [-WhatIf [<Swit
chParameter>]] [<CommonParameters>]
Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -Password <SecureString> [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-EmailNotification <Int32>] [-PreExpireDays <Int32>] [-Schedule <String>] [-WhatIf [<SwitchParameter>]] [<
CommonParameters>]
Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -ConfirmPassword <SecureString> -NewPassword <SecureString> [-AssignmentColl
ection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-EmailNotification <Int32>] [-PreExpireDays <Int32>] [-Schedule <String
>] [-SetNewPassword <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPManagedAccount [-Identity] <SPManagedAccountPipeBind> -ExistingPassword <SecureString> [-AssignmentCollection <SPAssignmentCollect
ion>] [-Confirm [<SwitchParameter>]] [-EmailNotification <Int32>] [-PreExpireDays <Int32>] [-Schedule <String>] [-UseExistingPassword <S
witchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$m = Get-SPManagedAccount -Identity "DOMAINx\UserY"

C:\PS>Set-SPManagedAccount -Identity $m -AutoGeneratePassword true
]]>
        </Code>
        <Remarks>
          This example displays an explicit managed account if it exists, and then attempts to update it to use automatically generated pas
          swords
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPMetadataServiceApplication </name>
    <synopsis><![CDATA[ Sets the properties for a Metadata Service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Set-SPMetadataServiceApplication cmdlet to set the properties for a service application for the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPMetadataServiceApplication -Identity <SPMetadataServiceCmdletPipeBind> [-AdministratorAccount <String>] [-ApplicationPool <SPIisWe
bServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-CacheTimeCheckInterval <Int32>] [-Confirm [<SwitchP
arameter>]] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-DoNotUnpublishAllPackages <Switc
hParameter>] [-FailoverDatabaseServer <String>] [-FullAccessAccount <String>] [-HubUri <String>] [-MaxChannelCache <Int32>] [-Name <Stri
ng>] [-RestrictedAccount <String>] [-SyndicationErrorReportEnabled <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE 1--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPMetadataServiceApplication -Identity "MetadataServiceApp1" -HubUri "http://sitename" -SyndicationErrorReportEnabled
]]>
        </Code>
        <Remarks>
          This example sets a content type hub to be used for syndication on an existing Metadata Service application. It also enables erro
          r reporting during syndication. Note that the HubUri parameter can only be set once
        </Remarks>
      </example>
      <example>
        <title> --------------------EXAMPLE 2--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPMetadataServiceApplication -Identity "MetadataServiceApp1" -AdministratorAccount "contoso\username1" -FullAccessAccount "con
toso\AppPoolAccount1,contoso\AppPoolAccount2" -RestrictedAccount "contoso\AppPoolAccount3,contoso\AppPoolAccount4,contoso\AppPoolAccount
5"
]]>
        </Code>
        <Remarks>
          This example sets permissions on an existing Metadata Service application. Note that setting any of these permissions replaces al
          l previous permission settings on the Metadata Service application
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPMetadataServiceApplicationProxy </name>
    <synopsis><![CDATA[ Sets the properties for a Metadata Service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ Use the Set-SPMetadataServiceApplicationProxy cmdlet to set the properties for a Metadata Service application proxy For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPMetadataServiceApplicationProxy -Identity <SPMetadataServiceProxyCmdletPipeBind> [-AssignmentCollection <SPAssignmentCollection>] 
[-Confirm [<SwitchParameter>]] [-ContentTypePushdownEnabled <SwitchParameter>] [-ContentTypeSyndicationEnabled <SwitchParameter>] [-Defa
ultKeywordTaxonomy <SwitchParameter>] [-DefaultProxyGroup <SwitchParameter>] [-DefaultSiteCollectionTaxonomy <SwitchParameter>] [-Name <
String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE 1--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1" -ContentTypeSyndicationEnabled -ContentTypePushdownEnabled
]]>
        </Code>
        <Remarks>
          This example enables content type syndication and enables content type pushdown on an existing Metadata Service application proxy
          
        </Remarks>
      </example>
      <example>
        <title> -----------------EXAMPLE 2--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1" -ContentTypeSyndicationEnabled:$false -ContentTypePushdown
Enabled:$false
]]>
        </Code>
        <Remarks>
          This example disables content type syndication and disables content type pushdown on an existing Metadata Service application pro
          xy
        </Remarks>
      </example>
      <example>
        <title> -----------------EXAMPLE 3--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPMetadataServiceApplicationProxy -Identity "MetadataServiceProxy1" -DefaultKeywordTaxonomy -DefaultSiteCollectionTaxonomy:$fa
lse
]]>
        </Code>
        <Remarks>
          This example configures an existing Metadata Service application proxy to be the default location for storing metadata keywords a
          nd prevents it from being the default location for creating site collection term sets
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPMobileMessagingAccount </name>
    <synopsis><![CDATA[ Configures the specified mobile messaging account. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPMobileMessagingAccount cmdlet configures the specified mobile messaging account For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPMobileMessagingAccount [-Identity] <SPMobileMessagingAccountPipeBind> -WebApplication <SPWebApplicationPipeBind> [-AssignmentColle
ction <SPAssignmentCollection>] [-Password <String>] [-ServiceName <String>] [-ServiceUrl <String>] [-UserId <String>] [<CommonParameter
s>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPMobileMessagingAccount -WebApplication http://sitename -Identity SMS -ServiceName SMSLink -ServiceUrl https://www.adatum.com
/Service/MessagingService.asmx-UserId someone@example.com -Password password1
]]>
        </Code>
        <Remarks>
          This example changes the SMS mobile account settings of the Web application, http://sitename, to the following values:
          service name: SMSLink; service URL: https://www.adatum.com/Service/MessagingService.asmx; user ID: someone@example.com; and password: pas
          sword1
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPPassPhrase </name>
    <synopsis><![CDATA[ Sets the pass phrase to a new value. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPPassPhrase cmdlet sets the Passphrase to a new Passphrase value. If the LocalServerOnly parameter is not used, the farm
 encryption key is re-encrypted with the new value and attempts to propagate this value to all other servers in the farm. If the LocalSer
verOnly parameter is used, this is updated on the local machine only, and the farm encryption key is not changed. The Passphrase value mu
st be the same on all servers in the farm if the farm is to function correctly. So if the Passphrase fails to propagate to all servers, t
he LocalServerOnly parameter can be used to set the remaining servers to the new Passphrase value manually For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPPassPhrase -ConfirmPassPhrase <SecureString> -PassPhrase <SecureString> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm
 [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPPassPhrase -PassPhrase <SecureString> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-LocalServe
rOnly <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$passphrase = ConvertTo-SecureString -asPlainText -Force

C:\PS>Set-SPPassPhrase -PassPhrase $passphrase -Confirm
]]>
        </Code>
        <Remarks> This example queries for a string to use as a passphrase, and sets the farm passphrase to a new value </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPPerformancePointSecureDataValues </name>
    <synopsis><![CDATA[ Sets global settings for the unattended service account. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPPerformancePointSecureDataValues cmdlet sets global settings and properties for the unattended service account For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPPerformancePointSecureDataValues [-ServiceApplication] <SPPerformancePointMonitoringServiceApplicationPipeBind> -DataSourceUnatten
dedServiceAccount <PSCredential> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParame
ter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE 1-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPPerformancePointSecureDataValues -ServiceApplication "PerformancePoint Service Application" -DataSourceUnattendedServiceAcco
unt (get-credential)
]]>
        </Code>
        <Remarks> This example shows how to set the unattended service account by prompting the user for the user name and password </Remarks>
      </example>
      <example>
        <title> --------------------EXAMPLE 2-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPPerformancePointSecureDataValues -ServiceApplication "PerformancePoint Service Application" -DataSourceUnattendedServiceAcco
unt (New-Object System.Management.Automation.PSCredential "domain\user", (ConvertTo-SecureString "password" -AsPlainText -Force))
]]>
        </Code>
        <Remarks>
          This example shows how to pass the user name and password as parameters to the cmdlet The DataSourceUnattendedServiceAccount parameter accepts a PSCredential object. Therefore, to pass in this value as a parameter,
          a new PSCredential object must be created using the desired username and password values. The PSCredential object requires that the passw
          ord be given as a SecureString type
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPPerformancePointServiceApplication </name>
    <synopsis><![CDATA[ Sets global runtime properties for a PerformancePoint Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPPerformancePointServiceApplication cmdlet updates global runtime properties for a PerformancePoint Service application.
 The changes made to properties by using this cmdlet affect all servers in the farm that run the instance of the specified PerformancePoi
nt Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPPerformancePointServiceApplication [-Identity] <SPPerformancePointMonitoringServiceApplicationPipeBind> [-AnalyticQueryCellMax <In
t32>] [-AnalyticQueryLoggingEnabled <$true | $false>] [-ApplicationCacheEnabled <$true | $false>] [-ApplicationCacheMinimumHitCount <Int
32>] [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-ApplicationProxyCacheEnabled <$true | $false>] [-AssignmentCollection
 <SPAssignmentCollection>] [-CommentsDisabled <$true | $false>] [-CommentsScorecardMax <Int32>] [-Confirm [<SwitchParameter>]] [-DataSou
rceQueryTimeoutSeconds <Int32>] [-DecompositionTreeMaximum <Int32>] [-ElementCacheSeconds <Int32>] [-FilterRememberUserSelectionsDays <I
nt32>] [-FilterTreeMembersMax <Int32>] [-IndicatorImageCacheSeconds <Int32>] [-MSMQEnabled <$true | $false>] [-MSMQName <String>] [-Sele
ctMeasureMaximum <Int32>] [-SessionHistoryHours <Int32>] [-SettingsDatabase <String>] [-ShowDetailsInitialRows <Int32>] [-ShowDetailsMax
Rows <Int32>] [-ShowDetailsMaxRowsDisabled <$true | $false>] [-TrustedContentLocationsRestricted <$true | $false>] [-TrustedDataSourceLo
cationsRestricted <$true | $false>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPPerformancePointServiceApplication -Identity PPSApp_01 -DataSourceQueryTimeoutSeconds 5000
]]>
        </Code>
        <Remarks>
          This example sets the Data Source Query Timeout setting to a value of 5000. This cmdlet is equivalent to the PerformancePoint Ser
          vice Settings page on the SharePoint Central Administration Web site
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPProfileServiceApplication </name>
    <synopsis><![CDATA[ Sets properties of a User Profile Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPProfileServiceApplication cmdlet sets properties of a User Profile Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPProfileServiceApplication [-Identity] <SPServiceApplicationPipeBind> [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [
-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MySiteHostLocation <SPSitePipeBind>] [-Name <String>] [
-ProfileDBCredentials <PSCredential>] [-ProfileSyncDBCredentials <PSCredential>] [-SocialDBCredentials <PSCredential>] [-SyncInstanceMac
hine <SPServerPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPProfileServiceApplication [-Identity] <SPServiceApplicationPipeBind> -MySiteHostLocation <SPSitePipeBind> [-ApplicationPool <SPIis
WebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MySiteHostLocation
 <SPSitePipeBind>] [-MySiteManagedPath <SPPrefixPipeBind>] [-Name <String>] [-ProfileDBCredentials <PSCredential>] [-ProfileSyncDBCreden
tials <PSCredential>] [-SiteNamingConflictResolution <String>] [-SocialDBCredentials <PSCredential>] [-SyncInstanceMachine <SPServerPipe
Bind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$ap = Get-SPServiceApplication -Name PartitionedUserProfileApplication

C:\PS>#Change the name of the application
Set-SPProfileServiceApplication -Identity $ap -Name PartitionedUserProfileApplication2
]]>
        </Code>
        <Remarks> This example sets profile information by using the specified identity </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPProfileServiceApplicationProxy </name>
    <synopsis><![CDATA[ Sets properties of a proxy for a User Profile Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPProfileServiceApplicationProxy cmdlet sets properties of a proxy for a User Profile Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPProfileServiceApplicationProxy [-Identity] <SPServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-DefaultProxyGroup <SwitchParameter>] [-MySiteHostLocation <SPSitePipeBind>] [-MySiteManagedPath <SPPrefix
PipeBind>] [-Name <String>] [-SiteNamingConflictResolution <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>#Get UPA Proxy
$pr = Get-SPServiceApplicationProxy | ? {$_.DisplayName.Contains(PartitionedUserProfileApplication_Proxy)}

C:\PS>#Change the name of the proxy
Set-SPProfileServiceApplicationProxy -Identity $pr -Name PartitionedUserProfileApplication_Proxy2
]]>
        </Code>
        <Remarks> This example sets a proxy for the User Profile Service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPProfileServiceApplicationSecurity </name>
    <synopsis>
      <![CDATA[ Set-SPProfileServiceApplicationSecurity -Identity <SPObjectSecurity> -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind>
 [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-Type <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Verbose] [-Debug] [
-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>] [-OutVariable 
<String>] [-OutBuffer <Int32>] [-WhatIf] [-Confirm]
 ]]>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Set-SPProfileServiceApplicationSecurity -Identity <SPObjectSecurity> -ProfileServiceApplicationProxy <SPServiceApplicationProxyPipeBind>
 [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-Type <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Verbose] [-Debug] 
[-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>] [-OutVariabl
e <String>] [-OutBuffer <Int32>] [-WhatIf] [-Confirm]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSearchService </name>
    <synopsis>
      <![CDATA[ Set-SPSearchService [[-Identity] <SPSearchServicePipeBind>] [-CrawlAccount <String>] [-CrawlPassword <SecureString>] [-AddStartAddressFo
rNonNTZone <String>] [-MaxBackupDuration <String>] [-PerformanceLevel <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Verbos
e] [-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>] [
-OutVariable <String>] [-OutBuffer <Int32>]
 ]]>
    </synopsis>
    <description><![CDATA[ ]]></description>
    <syntax>
      <![CDATA[
Set-SPSearchService [[-Identity] <SPSearchServicePipeBind>] [-CrawlAccount <String>] [-CrawlPassword <SecureString>] [-AddStartAddressFo
rNonNTZone <String>] [-MaxBackupDuration <String>] [-PerformanceLevel <String>] [-AssignmentCollection <SPAssignmentCollection>] [-Verbo
se] [-Debug] [-ErrorAction <ActionPreference>] [-WarningAction <ActionPreference>] [-ErrorVariable <String>] [-WarningVariable <String>]
 [-OutVariable <String>] [-OutBuffer <Int32>]

]]>
    </syntax>
    <examples>
      <example>
        <title> </title>
        <Code>
          <![CDATA[
]]>
        </Code>
        <Remarks> </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSearchServiceInstance </name>
    <synopsis><![CDATA[ Sets properties of a search service instance. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSearchServiceInstance cmdlet modifies the SearchServiceInstance object For permissions and the most current information about Windows PowerShell for SharePoint Foundation 2010, see TechNet (http://go.
microsoft.com/fwlink/?LinkId=163184) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSearchServiceInstance -Identity <SPSearchServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-ProxyType <St
ring>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSearchServiceInstance -Local | Set-SPSearchServiceInstance -ProxyType proxy
]]>
        </Code>
        <Remarks> This example sets the local search service instance proxy type to proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSecureStoreApplication </name>
    <synopsis><![CDATA[ Sets properties of a Secure Store application. ]]></synopsis>
    <description><![CDATA[ The Set-SPSecureStoreApplication cmdlet sets properties of a Secure Store application ]]></description>
    <syntax>
      <![CDATA[
Set-SPSecureStoreApplication -Identity <SPSecureStoreApplication> [-Administrator <SPClaim[]>] [-AssignmentCollection <SPAssignmentColle
ction>] [-Confirm [<SwitchParameter>]] [-CredentialsOwnerGroup <SPClaim[]>] [-Fields <TargetApplicationField[]>] [-TargetApplication <Ta
rgetApplication>] [-TicketRedeemer <SPClaim[]>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$targetApp.FriendlyName = "Updated Contoso Target App"
Set-SPSecureStoreApplication -Identity $application -TargetApplication $targetApp
]]>
        </Code>
        <Remarks> This example sets a new display name Updated Contoso Target App for the target application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSecureStoreDefaultProvider </name>
    <synopsis><![CDATA[ Updates the secure store provider. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSecureStoreDefaultProvider cmdlet sets or replaces the secure store provider. To register a third-party secure store, i
mplement the ISecureStoreProvider interface. With the interface defined, place the DLL file in the global assembly cache, and then load t
he DLL and load the type, as shown in the example. You can then set the secure store provider ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSecureStoreDefaultProvider -Type <Type> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>[Reflection.Assembly]::LoadFrom("C:\ContosoFolder\contosoSecureStore.dll")

$type = [Contoso.SecureStore.ContosoSecureStoreProvider]
]]>
        </Code>
        <Remarks> This example sets the custom implemented secure store provider </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSecureStoreServiceApplication </name>
    <synopsis><![CDATA[ Sets properties of a Secure Store Service application in the farm. ]]></synopsis>
    <description><![CDATA[ The Set-SPSecureStoreServiceApplication cmdlet sets properties of a Secure Store Service application in the farm ]]></description>
    <syntax>
      <![CDATA[
Set-SPSecureStoreServiceApplication -Identity <SPServiceApplicationPipeBind> [-ApplicationPool <SPIisWebServiceApplicationPool>] [-Assig
nmentCollection <SPAssignmentCollection>] [-AuditingEnabled <SwitchParameter>] [-AuditlogMaxSize <Nullable>] [-Confirm [<SwitchParameter
>]] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-Datab
aseUsername <String>] [-FailoverDatabaseServer <String>] [-Sharing <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSecureStoreServiceApplication -Identity $contosoServApp -AuditlogMaxSize 40
]]>
        </Code>
        <Remarks> This example sets the maximum size of the audit log to 40 days for the given service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSecurityTokenServiceConfig </name>
    <synopsis><![CDATA[ Updates the settings of the SharePoint security token service (STS) identity provider. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSecurityTokenServiceConfig cmdlet updates the settings of the SharePoint security token service (STS) identity provider
. If a certificate file is used, the certificate must be an X509 certificate with private keys, otherwise an exception is raised This cmdlet operates only with certificates that can be exported. To create a certificate which can be used in this cmdlet specif
y the X509KeyStorageFlags.Exportable bit in the keyStorageFlags parameter of the x509Certificate2 object constructor For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSecurityTokenServiceConfig [-AssignmentCollection <SPAssignmentCollection>] [-FormsTokenLifetime <Int32>] [-ImportSigningCertifica
te <X509Certificate2>] [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] [-ServiceTokenCacheExpirationWindow <Int3
2>] [-ServiceTokenLifetime <Int32>] [-WindowsTokenLifetime <Int32>] [<CommonParameters>]
Set-SPSecurityTokenServiceConfig -SigningCertificateThumbprint <String> [-AssignmentCollection <SPAssignmentCollection>] [-FormsTokenLif
etime <Int32>] [-MaxLogonTokenCacheItems <Int32>] [-MaxServiceTokenCacheItems <Int32>] [-ServiceTokenCacheExpirationWindow <Int32>] [-Se
rviceTokenLifetime <Int32>] [-SigningCertificateStoreName <String>] [-WindowsTokenLifetime <Int32>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSecurityTokenServiceConfig - SigningCertificateThumbprint "2796BAE63F1801E277261BA0D77770028F20EEE4"
]]>
        </Code>
        <Remarks>
          This example updates the signing certificate of the SharePoint security token service (STS) identity provider with a certificate
          that has been deployed in the certificate store
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx
Enter password: ****
Set - SPSecurityTokenServiceConfig -ImportSingingCertificate $cert
]]>
        </Code>
        <Remarks> This example imports the signing certificate for the SharePoint STS identity provider </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPServiceApplication </name>
    <synopsis><![CDATA[ Sets properties of a service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Set-SPServiceApplication cmdlet to set various properties of a service application such as the default endpoint, and the 
application pool used by the service application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchP
arameter>]] [-DefaultEndpoint <SPServiceEndpointPipeBind>] [-IisWebServiceApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-Se
rviceApplicationProxyGroup <SPServiceApplicationProxyGroupPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>$serviceapp = Get-SPServiceApplication "My Service App"

C:\PS>Set-SPServiceApplication $serviceapp -DefaultEndpoint https
]]>
        </Code>
        <Remarks> This example sets the default endpoint of the service application to be https </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPServiceApplicationEndpoint </name>
    <synopsis><![CDATA[ Sets the host of an endpoint for a service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set- SPServiceApplicationEndpoint cmdlet sets the host of a service endpoint. Use the second parameter set to reset the host 
of the service endpoint to use the default endpoint For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPServiceApplicationEndpoint [-Identity] <SPServiceEndpointPipeBind> -HostName <String> [-AssignmentCollection <SPAssignmentCollecti
on>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPServiceApplicationEndpoint [-Identity] <SPServiceEndpointPipeBind> -ResetHostName <SwitchParameter> [-AssignmentCollection <SPAssi
gnmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPServiceApplicationEndpoint -Identity "ServiceApp1" -HostName http://sitename -ResetHostName $true
]]>
        </Code>
        <Remarks> This example associates the SPServiceEndpoint object with the specified identity and resets the hostname </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPServiceApplicationPool </name>
    <synopsis><![CDATA[ Changes the account used for the Identity of the specified application pool. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPServiceApplicationPool cmdlet changes the account used for the Identity of the specified application pool For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPServiceApplicationPool [-Identity] <SPIisWebServiceApplicationPoolPipeBind> [[-Account] <SPProcessAccountPipeBind>] [-AssignmentCo
llection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPServiceApplicationPool  TestServiceWebApplicationPool -Account testdomain\testuser1
]]>
        </Code>
        <Remarks>
          This example changes the identity of the selected service application pool For the Account parameter, the name of a managed account in the farm can be given. Use the Get-SPManagedAccount cmdlet to view th
          e existing managed account in the farm. Also, a process account from the output of the Get-SPProcessAccount cmdlet can be used
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPServiceApplicationSecurity </name>
    <synopsis><![CDATA[ Updates the SPObjectSecurity object for a service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPServiceApplicationSecurity cmdlet updates a security object for the specified service application. Use this cmdlet with
 the Grant-SPObjectSecurity and Get-SPServiceApplicationSecurity cmdlets to manage security for a service application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPServiceApplicationSecurity [-Identity] <SPServiceApplicationPipeBind> [-ObjectSecurity] <SPObjectSecurity> [-Admin <SwitchParamete
r>] [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$security = Get-SPServiceApplicationSecurity $serviceApp -Admin
Grant-SPObjectSecurity $security $principal "Full Control"
Set-SPServiceApplicationSecurity $serviceApp -Admin $security
]]>
        </Code>
        <Remarks>
          This example retrieves the SPObjectSecurity object corresponding to the administrator ACL on a service application, and adds a ne
          w user principal to that ACL. The new user is an administrator for the service application $serviceApp
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPServiceHostConfig </name>
    <synopsis><![CDATA[ Configures one or more common settings for all Web services. ]]></synopsis>
    <description>
      <![CDATA[ The Set- SPServiceHostConfig cmdlet configures one or more common settings for all Web services For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPServiceHostConfig [-Identity] <SPIisWebServiceSettings> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParamet
er>]] [-HttpPort <Int32>] [-HttpsPort <Int32>] [-ImportSslCertificate <X509Certificate2>] [-NetTcpPort <Int32>] [-NoWait <SwitchParamete
r>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPServiceHostConfig [-Identity] <SPIisWebServiceSettings> -SslCertificateThumbprint <String> [-AssignmentCollection <SPAssignmentCol
lection>] [-Confirm [<SwitchParameter>]] [-HttpPort <Int32>] [-HttpsPort <Int32>] [-NetTcpPort <Int32>] [-NoWait <SwitchParameter>] [-Ss
lCertificateStoreName <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPServiceHostConfig -Port 12345
]]>
        </Code>
        <Remarks> This example sets the HTTP port for the Web services </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSessionStateService </name>
    <synopsis><![CDATA[ Updates the credentials that are used to communicate with the state service database. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSessionStateService cmdlet updates the credentials that are used to communicate with the state service database For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSessionStateService [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCrede
ntial>] [-SessionTimeout <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSessionStateService -SessionTimeout 120
]]>
        </Code>
        <Remarks> This example changes the ASP.NET session state time-out to 2 hours </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSite </name>
    <synopsis><![CDATA[ Configures the specified sites. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSite cmdlet configures the site collection that is specified by the Identity parameter. If a parameter is not used, the
 value is not changed The QuotaTemplate parameter is mutually exclusive to the MaxSize parameter and WarningSize parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSite [-Identity] <SPSitePipeBind> [-AdministrationSiteType <None | TenantAdministration>] [-AssignmentCollection <SPAssignmentColl
ection>] [-Confirm [<SwitchParameter>]] [-LockState <String>] [-MaxSize <Int64>] [-OwnerAlias <SPUserPipeBind>] [-QuotaTemplate <SPQuota
TemplatePipeBind>] [-SecondaryOwnerAlias <SPUserPipeBind>] [-Template <SPWebTemplatePipeBind>] [-Url <String>] [-UserAccountDirectoryPat
h <String>] [-WarningSize <Int64>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPSite [-Identity] <SPSitePipeBind> [-AdministrationSiteType <None | TenantAdministration>] [-AssignmentCollection <SPAssignmentColl
ection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-SiteSubscription <SPSiteSubscriptionPipeBind>] [-WhatIf [<SwitchPar
ameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSite http://sitename/sites/teams/* | Set-SPSite -SecondaryOwner "DOMAIN\Jdoe"
]]>
        </Code>
        <Remarks> This example sets the secondary owner on a set of site collections to DOMAIN\Jdoe </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSite -identity "http://sitename" -MaxSize 4000000 -WarningSize 2000000
]]>
        </Code>
        <Remarks> This example configures the Quota settings for the site collection http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSiteAdministration </name>
    <synopsis><![CDATA[ Allows farm administrators to configure any site collection. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSiteAdministration cmdlet allows a farm administrator to configure particular settings on a site collection even if the
 farm administrator is not granted explicit permissions. Any parameter that is not provided is not changed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSiteAdministration [-Identity] <SPSiteAdministrationPipeBind> [-AdministrationSiteType <None | TenantAdministration>] [-Assignment
Collection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-LockState <String>] [-MaxSize <Int64>] [-OwnerAlias <SPUserPipeBin
d>] [-SecondaryOwnerAlias <SPUserPipeBind>] [-Template <SPWebTemplatePipeBind>] [-WarningSize <Int64>] [-WhatIf [<SwitchParameter>]] [<C
ommonParameters>]
Set-SPSiteAdministration [-Identity] <SPSiteAdministrationPipeBind> [-AdministrationSiteType <None | TenantAdministration>] [-Assignment
Collection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-SiteSubscription <SPSiteSubscriptionPip
eBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSiteAdministration http://sitename -OwnerAlias "DOMAIN\NewOwner"
]]>
        </Code>
        <Remarks> This example allows farm administrators to change the ownership of a site collection to which they do not have access </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSiteSubscriptionConfig </name>
    <synopsis><![CDATA[ Sets the configuration properties of a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSiteSubscriptionConfig cmdlet sets the configuration properties of a site subscription For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSiteSubscriptionConfig [-Identity] <SPSiteSubscriptionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switc
hParameter>]] [-FeaturePack <SPSiteSubscriptionFeaturePackPipeBind>] [-PassThru <SwitchParameter>] [-UserAccountDirectoryPath <String>] 
[-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSiteSubscription http://contoso.com -FeatureSet 12345678-90ab-cdef-1234-567890abcdef
]]>
        </Code>
        <Remarks> This example sets the Feature set of the entire site subscription that contains http://contoso.com with a Feature set GUID </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSiteSubscriptionEdiscoveryHub </name>
    <synopsis><![CDATA[ Sets properties for the eDiscovery hub of a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSiteSubscriptionEdiscoveryHub cmdlet sets global properties and settings for the Ediscovery hub For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSiteSubscriptionEdiscoveryHub -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>
]] [-SearchScope <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSiteSubscriptionEdiscoverySearchScope -Site http://contoso.com/sites/sitecollection1 -SearchScope 1
]]>
        </Code>
        <Remarks>
          This example enables the search scope for the entire site subscription. A value of zero (0) disables the search scope across the
          entire site subscription
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSiteSubscriptionMetadataConfig </name>
    <synopsis><![CDATA[ Sets the site subscription configuration settings for a specified Metadata Service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Set-SPSiteSubscriptionMetadataConfig cmdlet to set the site subscription-specific settings for a specified shared service
 application for the Metadata Service For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSiteSubscriptionMetadataConfig -Identity <SPSiteSubscriptionPipeBind> -ServiceProxy <SPMetadataServiceProxyCmdletPipeBind> [-Assig
nmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DoNotUnpublishAllPackages <SwitchParameter>] [-HubUri <String
>] [-SyndicationErrorReportEnabled <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPSiteSubscriptionMetadataConfig -Identity $siteSubscriptionPipeBind1 -ServiceProxy "MetadataServiceProxy2" -HubUri "http://si
tename" -SyndicationErrorReportEnabled:$false
]]>
        </Code>
        <Remarks>
          This example sets the content type syndication hub and disables syndication error reporting for a specific site subscription on a
          n existing partitioned Metadata Service application
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSiteSubscriptionProfileConfig </name>
    <synopsis><![CDATA[ Sets the parameters of a site subscription. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPSiteSubscriptionProfileConfig cmdlet sets the parameters of a site subscription For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> -ProfileServiceApplicationProxy <SPServiceApplicationProxyP
ipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MySiteHostLocation <SPSitePipeBind>] [-Synchr
onizationOU <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPSiteSubscriptionProfileConfig [-Identity] <SPSiteSubscriptionPipeBind> -MySiteHostLocation <SPSitePipeBind> -ProfileServiceApplica
tionProxy <SPServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-MySiteHo
stLocation <SPSitePipeBind>] [-MySiteManagedPath <SPPrefixPipeBind>] [-SiteNamingConflictResolution <String>] [-SynchronizationOU <Strin
g>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> Add code example </title>
        <Code>
          <![CDATA[
C:\PS>
]]>
        </Code>
        <Remarks>  </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPStateServiceApplication </name>
    <synopsis><![CDATA[ Updates the name of a state service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPStateServiceApplication cmdlet updates the name of a state service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPStateServiceApplication [-Identity] <SPStateServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm
 [<SwitchParameter>]] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPStateServiceApplication -Identity "State Service Application 1" -Name "New name for State Service Application 1"
]]>
        </Code>
        <Remarks> This example changes the display name of a state service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPStateServiceApplicationProxy </name>
    <synopsis><![CDATA[ Updates the name of a state service application proxy. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPStateServiceApplicationProxy cmdlet updates the name of a state service application proxy For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPStateServiceApplicationProxy [-Identity] <SPStateServiceApplicationProxyPipeBind> [-AssignmentCollection <SPAssignmentCollection>]
 [-Confirm [<SwitchParameter>]] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPServiceApplicationProxy -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -Name "New Service Application Proxy Name"
]]>
        </Code>
        <Remarks> This example changes the display name of a state service application proxy </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Updates properties of a state service database. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPStateServiceDatabase cmdlet manages the credentials that are used to communicate with the database, sets the weight of 
the database, or changes the state service application with which it is associated For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> [[-ServiceApplication] <SPStateServiceApplicationPipeBind>] [-Assignmen
tCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCredential>] [-Weight <Nullable>] [-WhatIf
 [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE 1-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -Weight 10
]]>
        </Code>
        <Remarks> This example updates the database weight to the maximum (10) </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 2-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b -ServiceApplication "StateSvcApp1"
]]>
        </Code>
        <Remarks> This example updates the associated service application for a state service database </Remarks>
      </example>
      <example>
        <title> --------------EXAMPLE 3-------------- </title>
        <Code>
          <![CDATA[
C:\PS>$cred = Get-Credential

C:\PS>Set-SPStateServiceDatabase -Identity "StateSvcDB1" -DatabaseCredentials $cred
]]>
        </Code>
        <Remarks> This example updates the SQL Authentication credentials that are used for a given database </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPSubscriptionSettingsServiceApplication </name>
    <synopsis><![CDATA[ Sets properties of a subscription settings service application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Set-SPSubscriptionSettingsServiceApplication cmdlet to set properties on a subscription settings service application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPSubscriptionSettingsServiceApplication [-Identity] <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>]
 [-Confirm [<SwitchParameter>]] [-DatabaseCredentials <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-FailoverData
baseServer <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE-------------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$applicationPool = GetSPIisWebServiceApplicationPool SettingsApplicationPool

C:\PS>Get-SPServiceApplication -Name SettingsServiceApp | Set-SPSubscriptionSettingsServiceApplication -ApplicationPool $applicationPool
]]>
        </Code>
        <Remarks>
          This example changes the application pool of the subscription settings service application. This command assumes that a subscript
          ion settings service application named SettingsServiceApp exists and that an application pool named SettingsApplicationPool exists} }
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPTimerJob </name>
    <synopsis><![CDATA[ Sets the schedule for running a timer job. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPTimerJob cmdlet sets the schedule for running a specified timer job For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Schedu
le <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTimerJob job-recycle-bin-cleanup | Set-SPTimerJob -Schedule "weekly at sat 5:00"
]]>
        </Code>
        <Remarks> This example sets the schedule to run the job-recylce-bin-cleanup timer job to weekly at sat 5:00 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPTopologyServiceApplication </name>
    <synopsis><![CDATA[ Sets the properties on the topology service application of the local farm. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPTopologyServiceApplication cmdlet sets the advanced properties of an application when the Identity parameter is used For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPTopologyServiceApplication [-Identity] <SPTopologyWebServiceApplicationPipeBind> -LoadBalancerUrl <String> [-AssignmentCollection 
<SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPTopologyServiceApplication 67877d63-bff4-4521-867a-ef4979ba07ce -LoadBalancedURL "https://testurl"
]]>
        </Code>
        <Remarks>
          This example sets the load-balanced URL for the topology service application The topology service application GUID is unique to every farm. You can run the Get-SPTopologyServiceApplication cmdlet to retriev
          e the GUID
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPTopologyServiceApplicationProxy </name>
    <synopsis><![CDATA[ Sets the proxy properties of the topology service application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPTopologyServiceApplicationProxy cmdlet sets the properties of the local topology service application proxy and the defa
ult load balancer For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPTopologyServiceApplicationProxy [-Identity] <SPTopologyWebServiceProxyPipeBind> -BadListPeriod <String> [-AssignmentCollection <SP
AssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPTopologyServiceApplicationProxy 67877d63-bff4-4521-867a-ef4979ba07ce -BadListPeriod 1234
]]>
        </Code>
        <Remarks>
          This example sets the bad list period for the given topology service application proxy The topology service application GUID is unique to every farm. You can run the Get-SPTopologyServiceApplication cmdlet to retriev
          e the GUID
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPTrustedIdentityTokenIssuer </name>
    <synopsis><![CDATA[ Sets the identity providers of a Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPTrustedIdentityTokenIssuer cmdlet sets the identity providers of a Web application or extended Web application. For the
 ASP.NET Membership provider and Role provider, this cmdlet changes the identity provider only if the result is piped to a variable and p
assed to a Web application. For security token service (STS) identity providers, this cmdlet changes the persisted identity provider obje
ct in the SPFarm object For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPTrustedIdentityTokenIssuer [-Identity] <SPTrustedIdentityTokenIssuerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-C
laimProvider <SPClaimProviderPipeBind>] [-ClaimsMappings <SPClaimMappingPipeBind[]>] [-Description <String>] [-ImportTrustCertificate <X
509Certificate2>] [-Realm <String>] [-SignInUrl <String>] [-UseWReply <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------------EXAMPLE 1---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPTrustedIdentityTokenIssuer "LiveIDSTS" -Certificate (Get-ChildItem"cert:Certificates (LocalComputer)\Personal\Certificates -
Name "LiveID Cert")
]]>
        </Code>
        <Remarks> This example sets the identity provider to LiveIDSTS </Remarks>
      </example>
      <example>
        <title> -------------------------EXAMPLE 2---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$ip = @( (Get-SPTrustedIdentityTokenIssuer "LiveID STS"), (New-SPTrustedIdentityTokenIssuer -ASPNetMembershipProvider "myMembershi
pProvider" -ASPNetRoleProvider "myRoleProvider"), (Get-SPTrustedIdentityTokenIssuer "NTLM")) )
New-SPWebApplication http://contoso.com -IdentityProvider $ip
]]>
        </Code>
        <Remarks>
          This example sets the identity provider using the .ASPNetMembership and Role parameters. When these parameters are used, a variab
          le must be set; otherwise, the values do not take effect
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPTrustedRootAuthority </name>
    <synopsis><![CDATA[ Creates a new trusted root authority. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPTrustedRootAuthority cmdlet creates a new trusted root authority. If a certificate file is used, the certificate must b
e an X509 certificate with private keys, otherwise an exception is raised For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPTrustedRootAuthority [-Identity] <SPTrustedRootAuthorityPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Certificate <
X509Certificate2>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx
Get - SPTrustedRootAuthority -Name "WFEFarm1" | Set- SPTrustedRootAuthority -Certificate $cert
]]>
        </Code>
        <Remarks> This example updates the certificate of the trusted root authority WFEFarm1 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPTrustedServiceTokenIssuer </name>
    <synopsis><![CDATA[ Updates a trust with the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPTrustedServiceTokenIssuer cmdlet updates a trust with a SharePoint farm. If a certificate file is used, it must have on
ly one X509 certificate without private keys, otherwise an exception is raised For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPTrustedServiceTokenIssuer [-Identity] <SPTrustedServiceTokenIssuerPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Cer
tificate <X509Certificate2>] [-Description <String>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$cert = Get-PfxCertificate C:\LiveIDSigningCert.pfx
Set - SPTrustedServiceTokenIssuer "WFEFarm1" - Description "WFE Farm 1" - ImportTrustCertificate $cert
]]>
        </Code>
        <Remarks> This example updates a SharePoint Farm trust using the trust certificate from a file </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set - SPTrustedServiceTokenIssuer "WFEFarm1" - Description "WFE Farm 1" -FederationMetadataUrl "https://liveid.com/STS/2007/03/fed
metadata.xml"
]]>
        </Code>
        <Remarks> This example updates a SharePoint farm trust using the trust certificate from the federation metadata endpoint URL </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPUsageApplication </name>
    <synopsis><![CDATA[ Sets properties of a usage application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPUsageApplication cmdlet sets properties of a usage application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPUsageApplication [-Identity] <SPUsageApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParam
eter>]] [-DatabaseName <String>] [-DatabasePassword <SecureString>] [-DatabaseServer <String>] [-DatabaseUsername <String>] [-EnableLogg
ing <SwitchParameter>] [-FailoverDatabaseServer <String>] [-UsageService <SPUsageServicePipeBind>] [-WhatIf [<SwitchParameter>]] [<Commo
nParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPUsageApplication -Identity "Usage and Health data collection" -DatabaseServer "Server Name" -DatabaseName "New Logging DB
]]>
        </Code>
        <Remarks> This example changes the database server and database name used by the usage logging service to store logging data </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPUsageDefinition </name>
    <synopsis><![CDATA[ Sets the retention period for a usage provider. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPUsageDefinition cmdlet sets the retention period for a specified usage provider. A usage definition object defines a sp
ecific type of usage provider For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPUsageDefinition [-Identity] <SPUsageDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParamet
er>]] [-DaysRetained <Int32>] [-Enable <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE-------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPUsageDefinition -Identity "Page Requests" -DaysRetained 31
]]>
        </Code>
        <Remarks> This example sets the number of days that stores page requests usage data to 31 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPUsageService </name>
    <synopsis><![CDATA[ Sets the properties of a usage service. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPUsageService cmdlet updates the properties of a usage service. If the Identity parameter is not specified, the cmdlet a
pplies the changes to the local usage service For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPUsageService [[-Identity] <SPUsageServicePipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]
] [-LoggingEnabled <Nullable>] [-UsageLogCutTime <UInt32>] [-UsageLogLocation <String>] [-UsageLogMaxSpaceGB <UInt32>] [-WhatIf [<Switch
Parameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPUsageService -LoggingEnabled $false

C:\PS>Set-SPUsageService -UsageLogLocation "d:\\testusagelogdir

C:\PS>Set-SPUsageService -UsageLogCutTime 5
]]>
        </Code>
        <Remarks>
          The examples disable usage logging, change the directory where usage files are stored, and creates a new usage log file every 5 m
          inutes
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPUser </name>
    <synopsis><![CDATA[ Configures properties on an existing user. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPUser cmdlet configures properties on an existing user For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPUser [-Identity] <SPUserPipeBind> [-AddPermissionLevel <String[]>] [-AssignmentCollection <SPAssignmentCollection>] [-ClearPermiss
ions <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-DisplayName <String>] [-Email <String>] [-Group <SPGroupPipeBind>] [-IsSiteColl
ectionAdmin <SwitchParameter>] [-MobileNumber <String>] [-PassThru <SwitchParameter>] [-RemovePermissionLevel <String[]>] [-SyncFromAD <
SwitchParameter>] [-Web <SPWebPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPUser -Identity 'Contoso\jdoe' -Web http://test -AddPermissionLevel "Contributor"
]]>
        </Code>
        <Remarks> This example sets a user (Contoso\jdoe) to be a contributor on http://test </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWeb </name>
    <synopsis><![CDATA[ Configures the specified subsite. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPWeb cmdlet configures the subsite specified by the Identity parameter. Settings for any parameters that are not provide
d are not changed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPWeb [-Identity] <SPWebPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Description <Str
ing>] [-RelativeUrl <String>] [-Template <SPWebTemplatePipeBind>] [-Theme <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWeb http://sitename/subweb | Set-SPWeb -Title "My Site Title"
]]>
        </Code>
        <Remarks> This example sets the title of an existing subsite </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWebAnalyticsServiceApplication </name>
    <synopsis><![CDATA[ Sets properties of a Web Analytics Service application. ]]></synopsis>
    <description><![CDATA[ The Set-WebAnalyticsServiceApplication cmdlet sets the properties of a Web Analytics Service application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http:} } ]]></description>
    <syntax>
      <![CDATA[
Set-SPWebAnalyticsServiceApplication [-Identity] <WebAnalyticsServiceApplicationPipeBind> [-ApplicationPool <SPIisWebServiceApplicationP
oolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-EnableDataTrimming <SwitchParameter>] [-
ListOfReportingDatabases <String>] [-ListOfStagingDatabases <String>] [-MaxAggregationLevel <String>] [-MinAggregationLevel <String>] [-
ReportConsolidationStartTime <Int32>] [-ReportingDataRetentionPeriod <Int32>] [-SamplingRate <Int32>] [-WhatIf [<SwitchParameter>]] [<Co
mmonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -------------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPWebAnalyticsServiceApplication -Identity WebAnalyticsServiceApplication1 -ReportingDataRetention 20 -SamplingRate 90
]]>
        </Code>
        <Remarks>
          This example sets the reporting data retention and sampling rate for a Web Analytics Service application named WebAnalyticsServic
          eApplication1
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWebAnalyticsServiceApplicationProxy </name>
    <synopsis><![CDATA[ Sets a new proxy for the Web Analytics Service application. ]]></synopsis>
    <description><![CDATA[ The Set-SPWebAnalyticsServiceApplicationProxy sets a new Web Analytics Service application proxy to the farm For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http:} } ]]></description>
    <syntax>
      <![CDATA[
Set-SPWebAnalyticsServiceApplicationProxy [-Identity] <WebAnalyticsServiceApplicationProxyPipeBind> [-ViewDataPermissionLevel] <String> 
[-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------------EXAMPLE---------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPWebAnalyticsServiceApplicationProxy -Identity "web analytics service application" -ViewDataPermissionLevel High
]]>
        </Code>
        <Remarks> This example sets the Web Analytics Service application proxy permission level to High </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWebApplication </name>
    <synopsis><![CDATA[ Configures the specified Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPWebApplication cmdlet configures the Web application specified by the Identity parameter. For any settings that are zon
e-specific (for the Zone parameter set), the zone to configure must be provided. The provided zone must already exist For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPWebApplication [-Identity] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter
>]] [-DefaultQuotaTemplate <String>] [-DefaultTimeZone <Int32>] [-Force <SwitchParameter>] [-ServiceApplicationProxyGroup <SPServiceAppl
icationProxyGroupPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPWebApplication [-Identity] <SPWebApplicationPipeBind> -Zone <Default | Intranet | Internet | Custom | Extranet> [-AdditionalClaimP
rovider <SPClaimProviderPipeBind[]>] [-AssignmentCollection <SPAssignmentCollection>] [-AuthenticationMethod <String>] [-AuthenticationP
rovider <SPAuthenticationProviderPipeBind[]>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-SignInRedirectProvider <SPTrus
tedIdentityTokenIssuerPipeBind>] [-SignInRedirectURL <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Set-SPWebApplication [-Identity] <SPWebApplicationPipeBind> -SMTPServer <String> [-AssignmentCollection <SPAssignmentCollection>] [-Conf
irm [<SwitchParameter>]] [-Force <SwitchParameter>] [-OutgoingEmailAddress <String>] [-ReplyToEmailAddress <String>] [-WhatIf [<SwitchPa
rameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://somesite | Set-SPWebApplication -Zone "Extranet" -HostHeader "http://www.contoso.com" - AllowAnonymous
Access
]]>
        </Code>
        <Remarks>
          This example sets the HostHeader URL for the Extranet zone of the given Web application as http://www.contoso.com and enables ano
          nymous access
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWebApplicationHttpThrottlingMonitor </name>
    <synopsis><![CDATA[ Sets the Health Score bucket values for an existing network throttling performance counter for a specified Web application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPWebApplicationHttpThrottlingMonitor cmdlet sets the Health Score bucket values for an existing network throttling perfo
rmance counter for a specified Web application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPWebApplicationHttpThrottlingMonitor [-Identity] <SPWebApplicationPipeBind> [-Category] <String> [-Counter] <String> [-AssignmentCo
llection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-HealthScoreBuckets <Double[]>] [-Instance <String>] [-IsDESC <Switch
Parameter>] [-LowerLimit <Double>] [-UpperLimit <Double>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$buckets=(2000,1000,500,300,200,100,50,30,20,10)
Set-SPWebApplicationHttpThrottlingMonitor http://sharepoint -
Category Memory -Counter 'Available Mbytes' -IsDesc -HealthScoreBuckets $buckets
]]>
        </Code>
        <Remarks>
          This example sets the Health Score bucket values for the Memory\Available Mbytes counter to the array listed for the http://share
          point Web application
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPWebApplicationHttpThrottlingMonitor http://sharepoint
0 -Category Memory -Counter 'Available Mbytes' -IsDesc -UpperLimit 3000
]]>
        </Code>
        <Remarks>
          This example sets the upper limit for the Memory\Available Mbytes counter, the highest value in the Health Score buckets, to 3000
          for the the http://sharepoint Web application
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWebTemplate </name>
    <synopsis><![CDATA[ Changes the title and description of an installed site template. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPWebTemplate cmdlet changes the title and description of an installed site template For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPWebTemplate [-Identity] <SPWebTemplatePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-
Description <String>] [-Name <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPSiteTemplate "ATH#0" | Set-SPSiteTemplate -name "Athletics Site"

C:\PS>Set-SPSiteTemplate "ATH#0" -name "Athletics Site"
]]>
        </Code>
        <Remarks> This examples change the ATH#0 template title to Athletics Site </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWordConversionServiceApplication </name>
    <synopsis><![CDATA[ Sets properties of a Word Automation Services application. ]]></synopsis>
    <description>
      <![CDATA[ The Set-SPWordConversionServiceApplication cmdlet sets global properties of a Word Automation Services application For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPWordConversionServiceApplication -Identity <WordServiceApplicationPipeBind> [-ActiveProcesses <Nullable>] [-AddSupportedFormats <S
tring[]>] [-ApplicationPool <SPIisWebServiceApplicationPoolPipeBind>] [-AssignmentCollection <SPAssignmentCollection>] [-ClearSupportedF
ormats <SwitchParameter>] [-Confirm [<SwitchParameter>]] [-ConversionsPerInstance <Nullable>] [-ConversionTimeout <Nullable>] [-Database
Credential <PSCredential>] [-DatabaseName <String>] [-DatabaseServer <String>] [-DisableBinaryFileScan <SwitchParameter>] [-DisableEmbed
dedFonts <SwitchParameter>] [-KeepAliveTimeout <Nullable>] [-MaximumConversionAttempts <Nullable>] [-MaximumConversionTime <Nullable>] [
-MaximumMemoryUsage <Nullable>] [-RecycleProcessThreshold <Nullable>] [-RemoveSupportedFormats <String[]>] [-TimerJobFrequency <Nullable
>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPServiceApplication -Name WordServices1 | Set-SPWordConversionServiceApplication -TimerJobFrequency 30
]]>
        </Code>
        <Remarks> This example sets the timer job frequency of the WordServices1 application to 30 minutes </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Set-SPWorkflowConfig </name>
    <synopsis><![CDATA[ Configures the workflow settings for the specified Web application. ]]></synopsis>
    <description>
      <![CDATA[ Use the Set-SPWorkflowConfig cmdlet to configure the workflow settings for the specified Web application For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Set-SPWorkflowConfig [-WebApplication] <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-DeclarativeWorkflow
sEnabled <$true | $false>] [-EmailNoPermissionParticipantsEnabled <$true | $false>] [-SendDocumentToExternalParticipants <$true | $false
>] [<CommonParameters>]
Set-SPWorkflowConfig [-SiteCollection] <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-DeclarativeWorkflowsEnabled <
$true | $false>] [-EmailNoPermissionParticipantsEnabled <$true | $false>] [-SendDocumentToExternalParticipants <$true | $false>] [<Commo
nParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Set-SPWorkflowConfig -webapplication http://sitename DeclarativeWorkflowsEnabled $true -EmailNoPermissionParticipantsEnabled $true
 -SendDocumentToExternalParticipants $false
]]>
        </Code>
        <Remarks>
          This example sets the workflow settings for the specified Web application to turn on declarative workflows, turn on e-mail to par
          ticipants who do not have permissions to the site, and turn off the functionality to send e-mail messages as attachments to external part
          icipants No return values. Use the Get-SPWorkflowConfig cmdlet to see values.
          To set farm-level workflow settings for event-delivery time-out and to postpone threshold and batch size, use Set-SPFarmConfig
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPAdminJob </name>
    <synopsis><![CDATA[ Immediately starts any waiting administrative job on the local computer. ]]></synopsis>
    <description>
      <![CDATA[ Use the Start-SPAdminJob cmdlet to execute all administrative timer jobs immediately rather than waiting for the timer job to run
 When the process account for the SharePoint 2010 Administration service (SPAdminV4)) is disabled (necessary in some installations
 for security reasons), the Start-SPAdminJob cmdlet must be run on all computers to perform provisioning and other administrative tasks t
hat SPAdmin ordinarily handles When you run this cmdlet in person (not in script), use the Verbose parameter to see the individual administrative operations tha
t are run For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPAdminJob [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonP
arameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPAdminJob -Verbose
]]>
        </Code>
        <Remarks> This example runs all waiting administrative jobs and shows verbose output to the administrator </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPAssignment </name>
    <synopsis><![CDATA[ Initiates a new assignment store. ]]></synopsis>
    <description>
      <![CDATA[ The Start-SPAssignment cmdlet properly disposes of objects used with variable assignments Large amounts of memory are often required when SPWeb, SPSite, or SPSiteAdminsitration objects are used. So the use of these obje
cts, or lists of these objects, in Windows PowerShell scripts requires proper memory management. By default, all Get commands dispose of 
these objects immediately after the pipeline finishes, but by using SPAssignment, you can assign the list of objects to a variable and di
spose of the objects after they are no longer needed. You can also ensure that the objects remain as long as you need them, even througho
ut multiple iterations of commands There are three levels of assignment:} } -- No assignment -- The object is not assigned to a variable and is disposed of after each iteration of the command -- Simple assignment -- All objects are assigned to the global assignment store. This is done by using the Global parameter. When
 using this level, all objects are assigned to a global store and are disposed of when the Stop-SPAssignment cmdlet is called -- Advanced assignment -- Objects are assigned to named stores for disposal. You can dispose of objects by using the Identity par
ameter with the Stop-SPAssignment cmdlet Regardless of the assignment level used, all objects are disposed of when the PowerShell runspace is closed For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPAssignment [-AssignmentCollection <SPAssignmentCollection>] [-Global <SwitchParameter>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPAssignment -global

C:\PS>$w = Get-SPWeb http://MyWeb

C:\PS>$w | Set-SPWeb -title "Accounting"

C:\PS>Stop-SPAssignment -global
]]>
        </Code>
        <Remarks>
          This example uses simple assignment. While easier to use simple assignment, running commands that iterate through multiple SPSite
          or SPWeb objects while simple assignment is enabled is not recommended. Ensure that Stop-SPAssignment is run before attempting any inter
          ations of multiple objects
        </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$gc = Start-SPAssignment

C:\PS>$web = $gc | Get-SPWeb http://MyWeb

C:\PS>$web | Set-SPWeb -title "Accounting"

C:\PS>Stop-SPAssignment -Identity $gc
]]>
        </Code>
        <Remarks>
          This example sets the title of the SPWeb object in multiple lines and controls the rate of disposal. This is an advanced example.
          Only developers are advised to use it
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPContentDeploymentJob </name>
    <synopsis><![CDATA[ Starts a content deployment job. ]]></synopsis>
    <description>
      <![CDATA[ The Start-SPContentDeploymentJob cmdlet starts a content deployment job For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPContentDeploymentJob -Identity <SPContentDeploymentJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-DeploySinceTime <String>] [-TestEnabled <SwitchParameter>] [-UseSpecificSnapshot <String>] [-WaitEnabled <SwitchParame
ter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPContentDeploymentPath "Path 1" | New-SPContentDeploymentJob -Name "Job 1" -SPContentDeploymentPath $_ -IncrementalEnabled:$t
rue -ScheduleEnabled:$false | Start-SPContentDeploymentJob
]]>
        </Code>
        <Remarks> This example creates a content deployment job Job 1 and runs it immediately </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance </name>
    <synopsis><![CDATA[ Starts an instance of a search manager service. ]]></synopsis>
    <description>
      <![CDATA[ The Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance cmdlet starts the query and site settings service instance on the
 server instance in the same farm as the search service application to host the query object model (OM), Windows Communication Foundation
 (WCF) endpoint, and query processor for the search service application For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance [-Identity] <SearchQueryAndSiteSettingsServiceInstancePipeBind> [-Assignment
Collection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$qssInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local
Start-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity $qssInstance
]]>
        </Code>
        <Remarks> This example starts the local query and site settings instance </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPEnterpriseSearchServiceInstance </name>
    <synopsis><![CDATA[ Starts an instance of a search service. ]]></synopsis>
    <description>
      <![CDATA[ The Start-SPEnterpriseSearchServiceInstance cmdlet starts an instance of a search service on a farm For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPEnterpriseSearchServiceInstance [-Identity] <SearchServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-C
onfirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceInstance -Local | Start-SPEnterpriseSearchServiceInstance
]]>
        </Code>
        <Remarks> This example starts the local search service instance </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPInfoPathFormTemplate </name>
    <synopsis><![CDATA[ Activates a previously quiesced Microsoft InfoPath 2010 form template. ]]></synopsis>
    <description>
      <![CDATA[ The Start-SPInfoPathFormTemplate cmdlet activates a previously quiesced InfoPath 2010 form template after the form is upgraded. D
uring update a form is quiesced, which disables access to the form For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPInfoPathFormTemplate -Identity <SPFormTemplatePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParam
eter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPInfoPathFormTemplate -Identity formName.xsn
]]>
        </Code>
        <Remarks> This example activates a form with a specified name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPServiceInstance </name>
    <synopsis><![CDATA[ Starts the service instance for a service on a specific server or the farm. ]]></synopsis>
    <description>
      <![CDATA[ Use the Start-SPServiceInstance cmdlet to start the service instance for a service on a specific server or on the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPServiceInstance [-Identity] <SPServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParam
eter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPServiceInstance 67877d63-bff4-4521-867a-ef4979ba07ce
]]>
        </Code>
        <Remarks>
          This example starts the given service instance on the server The service instance GUID is unique to every farm. You can run the Get-SPServiceInstance cmdlet to see the GUID of the service in
          stances, and then use the result from the SPServiceInstance cmdlet for other cmdlets
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Start-SPTimerJob </name>
    <synopsis><![CDATA[ Runs a timer job once. ]]></synopsis>
    <description>
      <![CDATA[ The Start-SPTimerJob cmdlet runs a timer job once on each front-end Web server where the parent service is provisioned For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Start-SPTimerJob [-Identity] <SPTimerJobPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-What
If [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> -----------------EXAMPLE---------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPTimerJob job-recycle-bin-cleanup | Start-SPTimerJob
]]>
        </Code>
        <Remarks> This example starts the timer job named, job-recycle-bin-cleanup </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Stop-SPAssignment </name>
    <synopsis><![CDATA[ Disposes of objects in the provided assignment collection. ]]></synopsis>
    <description>
      <![CDATA[ The Stop-SPAssignment cmdlet disposes of objects in the provided assignment collection. Use the Global parameter to dispose of al
l objects in the global assignment collector and to stop the global store from collecting additional objects. Provide a SemiGlobal assign
ment collector to dispose of all contained objects For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Stop-SPAssignment [[-SemiGlobal] <SPAssignmentCollection>] [-AssignmentCollection <SPAssignmentCollection>] [-Global <SwitchParameter>] 
[<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Start-SPAssignment -global

C:\PS>$w = Get-SPWeb http://MyWeb

C:\PS>$w | Set-SPWeb -title "Accounting"

C:\PS>Stop-SPAssignment -global
]]>
        </Code>
        <Remarks>
          This example uses simple assignment. While easier to use simple assignment, running commands that iterate through multiple SPSite
          or SPWeb objects while simple assignment is enabled is not recommended. Ensure that Stop-SPAssignment is run before attempting any itera
          tions of multiple objects
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance </name>
    <synopsis><![CDATA[ Stops an instance of a search manager service. ]]></synopsis>
    <description>
      <![CDATA[ The Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance cmdlet stops an instance of a search manager service For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance [-Identity] <SearchQueryAndSiteSettingsServiceInstancePipeBind> [-AssignmentC
ollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$qssInstance = Get-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Local
Stop-SPEnterpriseSearchQueryAndSiteSettingsServiceInstance -Identity $qssInstance
]]>
        </Code>
        <Remarks> This example stops the local query and site settings service instance </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Stop-SPEnterpriseSearchServiceInstance </name>
    <synopsis><![CDATA[ Stops an instance of a search service. ]]></synopsis>
    <description>
      <![CDATA[ The Stop-SPEnterpriseSearchServiceInstance cmdlet stops an instance of a search service For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Stop-SPEnterpriseSearchServiceInstance [-Identity] <SearchServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Co
nfirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceInstance -Local | Stop-SPEnterpriseSearchServiceInstance
]]>
        </Code>
        <Remarks> This example stops the local search service instance </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Stop-SPInfoPathFormTemplate </name>
    <synopsis><![CDATA[ Disables a Microsoft InfoPath 2010 form template on a farm before an upgrade. ]]></synopsis>
    <description>
      <![CDATA[ The Stop-SPInfoPathFormTemplate cmdlet quiesces, or disables, an InfoPath 2010 form template before it upgrades the form. Before 
a form is updated it is quiesced, which disables access to the form. Use Start-SPIPFormTemplate to unquiesce, or activate, a form templat
e after the form is upgraded For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Stop-SPInfoPathFormTemplate -Identity <SPFormTemplatePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParame
ter>]] [-TimeLeft <Nullable>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Stop-SPInfoPathFormTemplate -Identity formName.xsn
]]>
        </Code>
        <Remarks> This example disables a form template for a specified name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Stop-SPServiceInstance </name>
    <synopsis><![CDATA[ Stops the service instance for a service. ]]></synopsis>
    <description>
      <![CDATA[ Stops the service instance for a service on the specified server or for the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Stop-SPServiceInstance [-Identity] <SPServiceInstancePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParame
ter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Stop-SPServiceInstance 67877d63-bff4-4521-867a-ef4979ba07ce
]]>
        </Code>
        <Remarks>
          This example stops the service instance in the given server The service instance GUID is unique to every farm. You can run the Get-SPServiceInstance cmdlet to see the GUID of the service in
          stances, and then use the result from the SPServiceInstance cmdlet for other cmdlets
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Suspend-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Suspends a search service application, pausing all crawls and search operations, to perform a task such as system maintenance. ]]></synopsis>
    <description>
      <![CDATA[ The Suspend-SPEnterpriseSearchServiceApplication cmdlet reads the SearchServiceApplication object and moves it from the Online st
ate to the Paused for: External Request state For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Suspend-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollecti
on>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssa = Get-SPEnterpriseSearchServiceApplication -Identity MySSA
$ssa | Suspend-SPEnterpriseSearchServiceApplication
]]>
        </Code>
        <Remarks> This example obtains a reference to a search service application named MySSA and pauses it, stopping all crawls </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Suspend-SPStateServiceDatabase </name>
    <synopsis><![CDATA[ Pauses a state database and thus prevents new rows of data from being added to a database. ]]></synopsis>
    <description>
      <![CDATA[ The Suspend-SPStateServiceDatabase cmdlet pauses a state database. This cmdlet updates the state database object that is specifie
d in the Identity parameter For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Suspend-SPStateServiceDatabase [-Identity] <SPStateDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Switch
Parameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Suspend-SPStateServiceDatabase -Identity 9703f7e2-9521-47c3-bd92-80e3eeba391b
]]>
        </Code>
        <Remarks> This example suspends a specified state service database </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Test-SPContentDatabase </name>
    <synopsis><![CDATA[ Tests a content database. ]]></synopsis>
    <description>
      <![CDATA[ Use the Test-SPContentDatabase cmdlet to test a content database against a Web application to verify all customizations reference
d within the content database are also installed in the web application. This cmdlet can be issued against a content database currently a
ttached to the farm, or a content database that is not connected to the farm. It can be used to test content databases from SharePoint 20
10 Products and from SharePoint Products and Technologies The Test-SPContentDatabase cmdlet does not change any of the data or structure of the content database, but can cause load on the
 database while the checks are in progress, which could temporarily block use of the content database. This cmdlet should only be used ag
ainst a content database that is currently under low or no usage For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Test-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-DatabaseCredentials <P
SCredential>] [-ServerInstance <SPDatabaseServiceInstancePipeBind>] [-ShowRowCounts <SwitchParameter>] [<CommonParameters>]
Test-SPContentDatabase -Name <String> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Data
baseCredentials <PSCredential>] [-ServerInstance <SPDatabaseServiceInstancePipeBind>] [-ShowRowCounts <SwitchParameter>] [<CommonParamet
ers>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------------------EXAMPLE 1----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Test-SPContentDatabase -name WSS_Content_DB -webapplication http://sitename
]]>
        </Code>
        <Remarks> This example tests the WSS_Content_DB content database against the sitename Web application, and returns a list of issues </Remarks>
      </example>
      <example>
        <title> ----------------------------EXAMPLE 2----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>$DB = Get-SPContentDatabase -site http://contoso.com

C:\PS>Test-SPContentDatabase $DB -showrowcounts
]]>
        </Code>
        <Remarks>
          This example gets the content database that contains the site collection at http://contoso.com, and then tests the database again
          st the Web application that hosts it to determine issues. Together with displaying the list of issues, by specifying the ShowRowCounts pa
          rameter, this also returns the table size metrics from the content database
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Test-SPInfoPathFormTemplate </name>
    <synopsis><![CDATA[ Validates that a Microsoft InfoPath 2010 form template is browser-enabled. ]]></synopsis>
    <description>
      <![CDATA[ The Test-SPInfoPathFormTemplate cmdlet validates that an InfoPath 2010 form template can be browser-enabled For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Test-SPInfoPathFormTemplate -Path <String> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Test-SPInfoPathFormTemplate -Identity formName.xsn
]]>
        </Code>
        <Remarks> This example validates an InfoPath 2010 form template for a specified name </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Uninstall-SPDataConnectionFile </name>
    <synopsis><![CDATA[ Removes a data connection file. ]]></synopsis>
    <description>
      <![CDATA[ The Uninstall-SPDataConnectionFile cmdlet removes the data connection file specified in the Identity parameter For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Uninstall-SPDataConnectionFile -Identity <SPDataConnectionFilePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<Swi
tchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------EXAMPLE----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Uninstall-SPDataConnectionFile -Identity "Sample.udcx

C:\PS>"Sample1.udcx", "Sample2.udcx", "Sample3.udcx" | Uninstall-SPDataConnectionFile
]]>
        </Code>
        <Remarks> This example uninstalls a specified data connection file in two different ways </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Uninstall-SPFeature </name>
    <synopsis><![CDATA[ Uninstalls an installed feature definition. ]]></synopsis>
    <description>
      <![CDATA[ The Uninstall-SPFeature cmdlet removes the specified feature definition from the collection of feature definitions in the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Uninstall-SPFeature [-Identity] <SPFeatureDefinitionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParamet
er>]] [-Force <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Uninstall-SPFeature -path "MyCustomFeature"
]]>
        </Code>
        <Remarks>
          This example uninstalls the feature at $env:ProgramFiles\Common Files\Microsoft Shared Debug\Web Server Extensions\14\TEMPLATE\FE
          ATURES\MyCustomFeature/feature.xml
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Uninstall-SPHelpCollection </name>
    <synopsis><![CDATA[ Removes Help collection files. ]]></synopsis>
    <description>
      <![CDATA[ The Uninstall-SPHelpCollection cmdlet removes the specified Help collection files from the product Help library in the current fa
rm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Uninstall-SPHelpCollection -Name <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<Swi
tchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Uninstall-SPHelpCollection - Name "OSSAdmin.1033"
]]>
        </Code>
        <Remarks> This example uninstalls a Help collection. The folder name of the Help collection to uninstall is OSSAdmin.1033 </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Uninstall-SPSolution </name>
    <synopsis><![CDATA[ Retracts a deployed SharePoint solution. ]]></synopsis>
    <description>
      <![CDATA[ The Uninstall-SPSolution cmdlet retracts a deployed SharePoint solution in preparation for removing it from the farm entirely. Th
is cmdlet removes files from the front-end Web server. Use the Remove-SPSolution cmdlet to delete the solution package from the solution 
store of the farm; be sure to use the Remove-SPSolution cmdlet only after you have run Uninstall-SPSolution For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Uninstall-SPSolution [-Identity] <SPSolutionPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-
Language <UInt32>] [-Local <SwitchParameter>] [-Time <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Uninstall-SPSolution [-Identity] <SPSolutionPipeBind> -WebApplication <SPWebApplicationPipeBind> [-AssignmentCollection <SPAssignmentCol
lection>] [-Confirm [<SwitchParameter>]] [-Language <UInt32>] [-Local <SwitchParameter>] [-Time <String>] [-WhatIf [<SwitchParameter>]] 
[<CommonParameters>]
Uninstall-SPSolution [-Identity] <SPSolutionPipeBind> -AllWebApplications <SwitchParameter> [-AssignmentCollection <SPAssignmentCollecti
on>] [-Confirm [<SwitchParameter>]] [-Language <UInt32>] [-Local <SwitchParameter>] [-Time <String>] [-WhatIf [<SwitchParameter>]] [<Com
monParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Uninstall-SPUserSolution -Identity contoso_solution.wsp
]]>
        </Code>
        <Remarks> This example retracts the deployed SharePoint solution contoso_solution.wsp </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Uninstall-SPUserSolution </name>
    <synopsis><![CDATA[ Deactivates a sandboxed solution in a site collection. ]]></synopsis>
    <description>
      <![CDATA[ The Uninstall-SPUserSolution cmdlet deactivates a sandboxed solution in a site collection so that you can delete it by using the 
Remove-SPUserSolution cmdlet. A user solution is a sandboxed solution For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Uninstall-SPUserSolution [-Identity] <SPUserSolutionPipeBind> -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-
Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE--------------- </title>
        <Code>
          <![CDATA[
C:\PS>Uninstall-SPUserSolution -Identity contoso_solution.wsp -Site http://sitename
]]>
        </Code>
        <Remarks> This example deactivates the sandboxed solution contoso_solution.wsp on the site http://sitename </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Uninstall-SPWebPartPack </name>
    <synopsis><![CDATA[ Uninstalls the specified Web Part package. ]]></synopsis>
    <description>
      <![CDATA[ The Uninstall-SPWebPartPack cmdlet uninstalls the Web Part package specified by the Identity parameter For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Uninstall-SPWebPartPack [-Identity] <String> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Language 
<UInt32>] [-WebApplication <SPWebApplicationPipeBind>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE1------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Uninstall-SPWebPartPack  "mypart.wpp" -WebApplication http://portal
]]>
        </Code>
        <Remarks> This example uninstalls mypart.wpp to from the Web application http://portal </Remarks>
      </example>
      <example>
        <title> ------------------EXAMPLE2------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebPartPack -WebApplication http://portal | Uninstall-SPWebPartPack
]]>
        </Code>
        <Remarks> This example uninstalls all Web part packages from the Web application http://portal </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Uninstall-SPWebTemplate </name>
    <synopsis><![CDATA[ Uninstalls the given site template. ]]></synopsis>
    <description>
      <![CDATA[ The Uninstall-SPWebTemplate cmdlet uninstalls the given site template by providing a full identity For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Uninstall-SPWebTemplate [-Identity] <SPWebTemplatePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter
>]] [-Language <UInt32>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Uninstall-SPWebTemplate "mytemplate"

C:\PS>Get-SPWebTemplate "mytemplate" | Uninstall-SPWebTemplate
]]>
        </Code>
        <Remarks> This example removes a site template named mytemplate </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Unpublish-SPServiceApplication </name>
    <synopsis><![CDATA[ Stops sharing the specified service application outside the farm. ]]></synopsis>
    <description>
      <![CDATA[ Use the Unpublish-SPServiceApplication cmdlet to stop publishing the service application, specified by the Identity parameter, ou
tside the farm For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Unpublish-SPServiceApplication [-Identity] <SPServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<S
witchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>UnPublish-SPServiceApplication 053c34be-d251-488c-8e94-644eae94da26
]]>
        </Code>
        <Remarks>
          This example stops publishing of the specified service application outside the farm The service application GUID is unique to every farm. You can run the Get-SPServiceApplication cmdlet to see the GUID of the serv
          ice applications, and then use the result from the Get-SPServiceApplication cmdlet for other SPServiceApplication cmdlets; for example, G
          rant-SPServiceApplication or Publish-SPServiceApplication
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPFarmEncryptionKey </name>
    <synopsis><![CDATA[ Changes the value of the farm encryption key and, using the new key, re-encrypts all the data. ]]></synopsis>
    <description>
      <![CDATA[ The Update-SPFarmEncryptionKey cmdlet changes the farm encryption key to a new randomly generated value. When the new key is used
, all the data is re-encrypted For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPFarmEncryptionKey [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-Resume <SwitchParameter>] [
-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE----------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Update-SPFarmEncryptionKey -confirm
]]>
        </Code>
        <Remarks> This example changes the farm encryption key to a new value and re-encrypts all the data </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPInfoPathAdminFileUrl </name>
    <synopsis>
      <![CDATA[ Updates InfoPath form templates (.xsn files) and universal data connections (.udcx files), including all .xsn files and .udcx files that
 were deployed by an administrator. ]]>
    </synopsis>
    <description>
      <![CDATA[ The Update-SPInfoPathAdminFileUrl cmdlet updates data connections in administrator-approved InfoPath form templates (.xsn files) 
and universal data connections (.udcx files). This allows for InfoPath data connections that reference the current farm to be updated whe
n content is migrated to a different farm URL. This cmdlet cannot update any references to URLs that exist in form template business logi
c (code). Typically, this cmdlet is used with the Import-SPInfoPathAdministratorFiles cmdlet For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPInfoPathAdminFileUrl -Find <Uri> -Replace <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]]
 [-Scan <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://contoso2010 | Update-SPInfoPathAdminFileUrl
-find "http://contoso2007" 
-replace "http://contoso2010"
]]>
        </Code>
        <Remarks>
          This example updates data connections in administrator-approved InfoPath form templates and universal data connection files. Data
          connections that reference http://contoso 2007 are updated to reference http://contoso2010
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPInfoPathFormTemplate </name>
    <synopsis><![CDATA[ Upgrades all Microsoft InfoPath form templates on the farm. ]]></synopsis>
    <description>
      <![CDATA[ The Update-SPInfoPathFormTemplate cmdlet upgrades all the InfoPath form templates on a farm that were deployed by an administrato
r. Use this cmdlet after the farm is upgraded to a new version For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPInfoPathFormTemplate [-AssignmentCollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter
>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ---------------EXAMPLE-------------- </title>
        <Code>
          <![CDATA[
C:\PS>Update-SPInfoPathFormTemplate
]]>
        </Code>
        <Remarks> This example updates InfoPath form templates on the entire farm </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPInfoPathUserFileUrl </name>
    <synopsis><![CDATA[ Updates InfoPath form templates (.xsn files) and universal data connections (.udcx files). ]]></synopsis>
    <description>
      <![CDATA[ The Update-SPInfoPathAdminFileUrl cmdlet updates data connections in InfoPath form templates (.xsn files) and universal data conn
ections (.udcx files). This allows for InfoPath data connections that reference the current farm to be updated when content is migrated t
o a different farm URL For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPInfoPathUserFileUrl [-WebApplication] <SPWebApplicationPipeBind> -Find <Uri> -Replace <Uri> [-AssignmentCollection <SPAssignmen
tCollection>] [-Confirm [<SwitchParameter>]] [-Scan <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Update-SPInfoPathUserFileUrl [-ContentDatabase] <SPContentDatabasePipeBind> -Find <Uri> -Replace <Uri> [-AssignmentCollection <SPAssignm
entCollection>] [-Confirm [<SwitchParameter>]] [-Scan <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Update-SPInfoPathUserFileUrl [-Site] <SPSitePipeBind> -Find <Uri> -Replace <Uri> [-AssignmentCollection <SPAssignmentCollection>] [-Conf
irm [<SwitchParameter>]] [-Scan <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPWebApplication http://contoso2010 | Update-SPInfoPathUserFileUrl
-find "http://contoso2007" 
-replace "http://contoso2010"
]]>
        </Code>
        <Remarks>
          This example updates data connections in InfoPath form templates and universal data connection files, for all content under the W
          eb application http://contoso2010. Data connections that reference http://contoso2007 are updated to reference http://contoso2010
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPProfilePhotoStore </name>
    <synopsis><![CDATA[ Moves photos of a user. ]]></synopsis>
    <description>
      <![CDATA[ The Update-SPProfilePhotoStore cmdlet moves photos of all users from their source location to the My Site host picture library During the move operation, the original image is left as is and a thumbnail is created. If the move operation fails for certain u
sers for any reason, it simply moves on to the next user For permissions and the most current information about Windows PowerShell for SharePoint Server 2010, see TechNet (http://go.micr
osoft.com/fwlink/?LinkId=163183) ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPProfilePhotoStore -MySiteHostLocation <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Update-SPProfilePhotoStore -MySiteHostLocation http://mysites
]]>
        </Code>
        <Remarks> This example uploads photos to a specified My Site host location </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPSecureStoreApplicationServerKey </name>
    <synopsis><![CDATA[ Synchronizes the key on a Microsoft SharePoint server with the Secure Store master key. ]]></synopsis>
    <description>
      <![CDATA[ The Update-SPSecureStoreApplicationServerKey cmdlet synchronizes the key on a SharePoint server with the master key for the Secur
e Store service database Updating a server key is required when:} } ; Tag=* } ; Tag=* } ; Tag=* } ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPSecureStoreApplicationServerKey -Passphrase <String> -ServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-AssignmentC
ollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$newPassPhrase = "abcDEF123!"

Update-SPSecureStoreApplicationServerKey -ServiceApplicationProxy $contosoProxy -Passphrase $newPassPhrase
]]>
        </Code>
        <Remarks>
          This example synchronizes the passphrase of the server key on a SharePoint server with the master key for the Secure Store servic
          e database
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPSecureStoreCredentialMapping </name>
    <synopsis><![CDATA[ Sets a new credential mapping for a Secure Store Service application. ]]></synopsis>
    <description><![CDATA[ The Update-SPSecureStoreCredentialMapping cmdlet sets a new credential mapping for a Secure Store Service application ]]></description>
    <syntax>
      <![CDATA[
Update-SPSecureStoreCredentialMapping -Identity <SPSecureStoreApplication> -Principal <SPClaim> -Values <SecureString[]> [-AssignmentCol
lection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoTargetApplication"

$firstCredential = ConvertTo-SecureString "LOBDATABASE\jdoe" -AsPlainText -Force

$secondCredential = ConvertTo-SecureString "abcDEF123$%^" -AsPlainText -Force

$credentialValues = $firstCredential,$secondCredential

$userClaim = New-SPClaimsObject -User "CONTOSO\janedoe" -Type WindowsSamAccountName

Update-SPSecureStoreCredentialMapping -Identity $ssApp -Values $credentialValues -Principal $userClaim
]]>
        </Code>
        <Remarks>
          This example updates a credential mapping for the given site and the target application ContosoTargetApplication, for the user wi
          th the identity janedoe on domain CONTOSO. This user is mapped to a pair of credential values on the External System with a username of i
          dentity jdoe on domain LOBDATABASE and password abcDEF123$%^
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPSecureStoreGroupCredentialMapping </name>
    <synopsis><![CDATA[ Sets a new group credential mapping for a Secure Store Service application. ]]></synopsis>
    <description>
      <![CDATA[ The Update-SPSecureStoreGroupCredentialMapping cmdlet sets a new group credential mapping for a Secure Store Service application.
 Group credentials are a set of credentials that are associated with multiple identities. Target applications will get credentials for a 
Secure Store application by using the current user. If the current user meets the authorization rule defined in the Secure Store applicat
ion for the group credentials, then the data is provided ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPSecureStoreGroupCredentialMapping -Identity <SPSecureStoreApplication> -Values <SecureString[]> [-AssignmentCollection <SPAssig
nmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$ssApp = Get-SPSecureStoreApplication -ServiceContext http://contoso -Name "ContosoGroupTargetApplication"

$firstCredential = ConvertTo-SecureString "LOBDATABASE\fulltimeemployees" -AsPlainText -Force

$secondCredential = ConvertTo-SecureString "abcDEF123$%^" -AsPlainText -Force

$credentialValues = $firstCredential,$secondCredential

Update-SPSecureStoreGroupCredentialMapping -Identity $ssApp -Values $credentialValues
]]>
        </Code>
        <Remarks>
          This example adds a credential mapping for the target application ContosoGroupTargetApplication, for all users in this group targ
          et application. These users are mapped to a pair of credential values on the External System with a username of identity fulltimeemployee
          s on domain LOBDATABASE and with password abcDEF123$%^
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPSecureStoreMasterKey </name>
    <synopsis><![CDATA[ Changes the master key of a Secure Store Service application. ]]></synopsis>
    <description><![CDATA[ The Update-SPSecureStoreApplicationServerKey cmdlet changes the master key of a Secure Store Service application Updating the master key is required when:} } ; Tag=* } ; Tag=* } ; Tag=* } ]]></description>
    <syntax>
      <![CDATA[
Update-SPSecureStoreMasterKey -Passphrase <String> -ServiceApplicationProxy <SPServiceApplicationProxyPipeBind> [-AssignmentCollection <
SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$newPassPhrase = "abcDEF123!"
Update-SPSecureStoreMasterKey -ServiceApplicationProxy $contosoProxy -Passphrase $newPassPhrase
]]>
        </Code>
        <Remarks> This example creates a new master key for the given service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPSolution </name>
    <synopsis><![CDATA[ Upgrades a deployed SharePoint solution. ]]></synopsis>
    <description>
      <![CDATA[ The Install-SPSolution cmdlet upgrades a deployed SharePoint solution in the farm. Use this cmdlet only if a new solution contain
s the same set of files and features as the deployed solution. If files and features are different, the solution must be retracted and re
deployed by using the Uninstall-SPSolution and Install-SPSolution cmdlets, respectively For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPSolution [-Identity] <SPSolutionPipeBind> -LiteralPath <String> [-AssignmentCollection <SPAssignmentCollection>] [-CASPolicies 
<SwitchParameter>] [-Confirm [<SwitchParameter>]] [-Force <SwitchParameter>] [-GACDeployment <SwitchParameter>] [-Local <SwitchParameter
>] [-Time <String>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Update-SPSolution -Identity contoso_solution.wsp -LiteralPath c:\contoso_solution_v2.wsp -GACDeployment
]]>
        </Code>
        <Remarks> This example upgrades the deployed SharePoint solution  contoso_solution.wsp to the solution c:\contoso_solution_v2.wsp </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Update-SPUserSolution </name>
    <synopsis><![CDATA[ Upgrades an activated sandboxed solution in a farm. ]]></synopsis>
    <description>
      <![CDATA[ The Update-SPUserSolution cmdlet upgrades a sandboxed solution that has already been activated in a farm. A user solution is a sa
ndboxed solution. Before you use this cmdlet to upgrade the activated solution, use the Add-SPUserSolution cmdlet to upload the upgraded 
solution to the solution gallery For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Update-SPUserSolution [-Identity] <SPUserSolutionPipeBind> -Site <SPSitePipeBind> -ToSolution <SPUserSolutionPipeBind> [-AssignmentColle
ction <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE--------------------- </title>
        <Code>
          <![CDATA[
C:\PS>Update-SPUserSolution -Identity contoso_solution.wsp -Site http://sitename -ToSolution contoso_solution_v2.wsp
]]>
        </Code>
        <Remarks>
          This example upgrades the sandboxed solution contoso_solution.wsp in the site http://sitename to the sandboxed solution contoso_s
          olution_v2.wsp
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Upgrade-SPContentDatabase </name>
    <synopsis><![CDATA[ Upgrades a content database. ]]></synopsis>
    <description>
      <![CDATA[ The Upgrade-SPContentDatabase cmdlet upgrades a SharePoint content database. When the Upgrade-SPContentDatabase cmdlet is run, an
 upgrade of an existing content database attached to the current farm is intiated. This cmdlet begins a new upgrade session, which can be
 used either to resume a failed version-to-version or build-to-build upgrade of a content database or to begin a build-to-build upgrade o
f a content database For permissions and the most current information about Windows PowerShell for SharePoint Products, see the online documentation (
http://go.microsoft.com/fwlink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Upgrade-SPContentDatabase [-Identity] <SPContentDatabasePipeBind> [[-ForceDeleteLock] <SwitchParameter>] [-AssignmentCollection <SPAssig
nmentCollection>] [-Confirm [<SwitchParameter>]] [-ServerInstance <SPDatabaseServiceInstancePipeBind>] [-UpdateUserExperience <SwitchPar
ameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]
Upgrade-SPContentDatabase [[-ForceDeleteLock] <SwitchParameter>] -Name <String> -WebApplication <SPWebApplicationPipeBind> [-AssignmentC
ollection <SPAssignmentCollection>] [-Confirm [<SwitchParameter>]] [-ServerInstance <SPDatabaseServiceInstancePipeBind>] [-UpdateUserExp
erience <SwitchParameter>] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> --------------------------EXAMPLE------------------------------ </title>
        <Code>
          <![CDATA[
C:\PS>$contentdb = Get-SPContentDatabase | Where-Object {$_.Name -match "SQLSERVER1\WSS_Content"}

C:\PS>Upgrade-SPContentDatabase -Identity $contentdb
]]>
        </Code>
        <Remarks>
          This example selects a specific content database that is currently attached to the farm, and then initiates an upgrade session. T
          his process continues until the upgrade is complete and might take some time, depending upon the amount of changes that have to be made d
          uring the upgrade
        </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Upgrade-SPEnterpriseSearchServiceApplication </name>
    <synopsis><![CDATA[ Upgrades a search service application. ]]></synopsis>
    <description>
      <![CDATA[ The Upgrade-SPEnterpriseSearchServiceApplication cmdlet starts an upgrade process on a search service application. This cmdlet ru
ns the associated upgrade actions for the search service application. Also, you can upgrade multiple search service applications in paral
lel by launching several instances of this cmdlet. It is not necessary to run this cmdlet if you already have run the SharePoint Products
 Configuration Wizard For the upgrade process to run successful, all of the computers in the farm must have the same version of binaries installed For permissions and the most current information about search cmdlets, see the online documentation, (http://go.microsoft.com/fwl
ink/?LinkId=163185) ]]>
    </description>
    <syntax>
      <![CDATA[
Upgrade-SPEnterpriseSearchServiceApplication [-Identity] <SearchServiceApplicationPipeBind> [-AssignmentCollection <SPAssignmentCollecti
on>] [-Confirm [<SwitchParameter>]] [-WhatIf [<SwitchParameter>]] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ----------------EXAMPLE 1----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Get-SPEnterpriseSearchServiceApplication | Upgrade-SPEnterpriseSearchServiceApplication
]]>
        </Code>
        <Remarks> This example upgrades a search service application </Remarks>
      </example>
      <example>
        <title> ----------------EXAMPLE 2----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Upgrade-SPEnterpriseSearchServiceApplication -Identity 846ceb0b-31d6-4c79-82c1-3a9deafe0b45
]]>
        </Code>
        <Remarks> This example upgrades a search service application </Remarks>
      </example>
      <example>
        <title> ----------------EXAMPLE 3----------------- </title>
        <Code>
          <![CDATA[
C:\PS>Upgrade-SPEnterpriseSearchServiceApplication "DefaultSearchApplication"
]]>
        </Code>
        <Remarks> This example upgrades a search service application </Remarks>
      </example>
    </examples>
  </cmd>
  <cmd>
    <name> Upgrade-SPSingleSignOnDatabase </name>
    <synopsis><![CDATA[ Migrates the application definitions from Single Sign-On (SSO) database to Secure Store database as target applications. ]]></synopsis>
    <description>
      <![CDATA[ The Upgrade-SPSingleSignOnDatabase cmdlet migrates the application definitions from SSO database to Secure Store database as targ
et applications. Use the Upgrade-SPSingleSignOn cmdlet to convert an SSO database to a Secure Store database. SSO is a Microsoft SharePoi
nt Server feature. SSO functionality is performed by the Secure Store Service in Microsoft SharePoint Server 2010 ]]>
    </description>
    <syntax>
      <![CDATA[
Upgrade-SPSingleSignOnDatabase -SecureStoreConnectionString <String> -SecureStorePassphrase <SecureString> -SSOConnectionString <String>
 [-AssignmentCollection <SPAssignmentCollection>] [<CommonParameters>]

]]>
    </syntax>
    <examples>
      <example>
        <title> ------------------EXAMPLE------------------ </title>
        <Code>
          <![CDATA[
C:\PS>Upgrade-SPSingleSignOnDatabase -SSOConnectionString "Data Source=oldServer;Database=SSO;Trusted_Connection=yes;" -SecureStoreConne
ctionString "Data Source=CONTOSO\SQLDatabase;Database=ContosoSSDatabase;Trusted_Connection=yes;" -SecureStorePassphrase "abcDEF123!@#"
]]>
        </Code>
        <Remarks> This example migrates the SSO database at the SSO connection to a Secure Store database at the Secure Store connection </Remarks>
      </example>
    </examples>
  </cmd>
</cmdlets>
